Systems and user interfaces for dynamic and interactive table generation and editing based on automatic traversal of complex data structures including time varying attributes

ABSTRACT

Various systems and methods are provided for accessing and traversing one or more complex data structures and generating a functional user interface that can enable non-technical users to quickly and dynamically generate detailed reports (including tables, charts, and/or the like) of complex data including time varying attributes. The user interfaces are interactive such that a user may make selections, provide inputs, and/or manipulate outputs. In response to various user inputs, the system automatically calculates applicable time intervals, accesses and traverses complex data structures (including, for example, a mathematical graph having nodes and edges), calculates complex data based on the traversals and the calculated time intervals, displays the calculated complex data to the user, and/or enters the calculated complex data into the tables, charts, and/or the like. The user interfaces may be automatically updated based on a context selected by the user.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/962,987, filed Dec. 8, 2015, and titled “SYSTEMS AND USER INTERFACESFOR DYNAMIC AND INTERACTIVE TABLE GENERATION AND EDITING BASED ONAUTOMATIC TRAVERSAL OF COMPLEX DATA STRUCTURES INCLUDING TIME VARYINGATTRIBUTES,” which is a continuation of U.S. patent application Ser. No.14/643,999, filed Mar. 10, 2015, and titled “SYSTEMS AND USER INTERFACESFOR DYNAMIC AND INTERACTIVE TABLE GENERATION AND EDITING BASED ONAUTOMATIC TRAVERSAL OF COMPLEX DATA STRUCTURES INCLUDING TIME VARYINGATTRIBUTES,” which claims benefit of U.S. Provisional Patent ApplicationNo. 62/059,770, filed Oct. 3, 2014, and titled “SYSTEMS AND USERINTERFACES FOR DYNAMIC AND INTERACTIVE TABLE GENERATION AND EDITINGBASED ON AUTOMATIC TRAVERSAL OF COMPLEX DATA STRUCTURES INCLUDING TIMEVARYING ATTRIBUTES.” The entire disclosure of each of the above items ishereby made part of this specification as if set forth fully herein andincorporated by reference for all purposes, for all that it contains.

Any and all applications for which a foreign or domestic priority claimis identified in the Application Data Sheet as filed with the presentapplication are hereby incorporated by reference under 37 CFR 1.57.

TECHNICAL FIELD

Embodiments of present disclosure relate to systems and techniques foraccessing one or more databases in substantially real-time to provideinformation in an interactive user interface. More specifically,embodiments of the present disclosure relate to user interfaces fordynamically generating and displaying time varying complex data based onelectronic collections of data.

BACKGROUND

The approaches described in this section are approaches that could bepursued, but not necessarily approaches that have been previouslyconceived or pursued. Therefore, unless otherwise indicated, it shouldnot be assumed that any of the approaches described in this sectionqualify as prior art merely by virtue of their inclusion in thissection.

A report (such as a report including tables and/or charts of complexdata) is a way of presenting and conveying information, and is useful inmany fields (for example, scientific fields, financial fields, politicalfields, and/or the like). In many fields, computer programs may bewritten to programmatically generate reports or documents fromelectronic collections of data, such as databases. This approachrequires a computer programmer to write a program to access theelectronic collections of data and output the desired report ordocument. Typically, a computer programmer must determine the properformat for the report from users or analysts that are familiar with therequirements of the report. Some man-machine interfaces for generatingreports in this manner are software development tools that allow acomputer programmer to write and test computer programs. Followingdevelopment and testing of the computer program, the computer programmust be released into a production environment for use. Thus, thisapproach for generating reports may be inefficient because an entiresoftware development life cycle (for example, requirements gathering,development, testing, and release) may be required even if only oneelement or graphic of the report requires changing. Furthermore, thissoftware development life cycle may be inefficient and consumesignificant processing and/or memory resources.

SUMMARY

The systems, methods, and devices described herein each have severalaspects, no single one of which is solely responsible for its desirableattributes. Without limiting the scope of this disclosure, severalnon-limiting features will now be discussed briefly.

Embodiments of the present disclosure relate to a computer systemdesigned to provide interactive, graphical user interfaces (alsoreferred to herein as “user interfaces”) for enabling non-technicalusers to quickly and dynamically generate, edit, and update complexreports including tables and charts of data. The user interfaces areinteractive such that a user may make selections, provide inputs, and/ormanipulate outputs. In response to various user inputs, the systemautomatically accesses and traverses complex data structures (including,for example, a mathematical graph having nodes and edges), calculatescomplex data based on the traversals, and/or displays the calculatedcomplex data to the user. The displayed data may be rapidly manipulatedand automatically updated based on a context selected by the user, andthe system may automatically publish generated data in multiplecontexts.

The computer system (also referred to herein simply as the “system”) maybe useful to, for example, financial advisors, such as registeredinvestment advisors (RIAs) and their firms. Such RIA's often need toview data relating to investment holdings of clients for purposes ofanalysis, reporting, sharing, or recommendations. Client investments maybe held by individuals, partnerships, trusts, companies, and other legalentities having complex legal or ownership relationships. RIAs and otherusers may use the system to view complex holdings in a flexible way, forexample, by selecting different metrics and/or defining their own viewsand reports on-the-fly.

Current wealth management technology does not offer the capability togenerate views, reports, or other displays of data from complexinvestment holding structures in an interactive, dynamic, flexible,shareable, efficient way. Some existing wealth management systems arecustom-built and therefore relatively static in their viewingcapabilities, requiring programmers to make customized versions (asdescribed above). Other systems lack scalability and are time-consumingto use. Yet other systems consist of MICROSOFT VISUAL BASIC scriptswritten for use with MICROSOFT EXCEL spreadsheets. This type of systemis an awkward attempt to add some measure of flexibility to an otherwisestatic foundation.

Various embodiments of the present disclosure enable data generation anddisplay in fewer steps, result in faster creation of outputs (such astables and reports), consume less processing and/or memory resourcesthan previous technology, permit users to have less knowledge ofprogramming languages and/or software development techniques, and/orallow less technical users or developers to create outputs (such astables and/or reports) than the user interfaces described above. Thus,the user interfaces described herein are more efficient as compared toprevious user interfaces, and enable the user to cause the system toautomatically access and initiate calculation of complex dataautomatically. Further, by storing the data as a complex mathematicalgraph, outputs (for example, a table) need not be stored separately andthereby take additional memory. Rather, the system may render outputs(for example, tables) in real time and in response to user interactions,such that the system may reduce memory and/or storage requirements.

Further, various embodiments of the system further reduce memoryrequirements and/or processing needs and time via a complex graph datastructure. For example, as described below, common data nodes may beused in multiple graphs of various users and/or clients of a firmoperating the system. Utilization of common data nodes reduces memoryrequirements and/or processing requirements of the system.

Accordingly, in various embodiments the system may calculate data (viacomplex graph traversal described herein) and provide a unique andcompact display of calculated data based on time varying attributesassociated with the calculated data. In an embodiment, the data may bedisplayed in a table in which data is organized based on the timevarying attributes and dates associated with particular metricsspecified by the user and/or determined by the system. In someembodiments, when no metric values are associated with a particular itemof data, a portion of the table is left blank and/or omitted.

In various embodiments the system may calculate time intervalsapplicable to calculations of various metrics. For example, the systemmay calculate asset value metrics for which a single date or time isapplicable. In other examples, the system may calculate metrics thatspan periods of time such as a rate of return of an asset over a numberof years. Accordingly, the system may determine a set of time intervalsassociated with the metric, a set of time intervals associated withapplicable time varying attributes of graph data, and determine inintersection of the two sets of time intervals. The calculatedintersection of the sets of time intervals may then be inputted into thecomplex graph traversal process to calculate metric values for displayin compact and efficient user interfaces of the system.

Accordingly, in various embodiments, large amounts of data areautomatically and dynamically calculated interactively in response touser inputs, and the calculated data is efficiently and compactlypresented to a user by the system. Thus, in some embodiments, the userinterfaces described herein are more efficient as compared to previoususer interfaces in which data is not dynamically updated and compactlyand efficiently presented to the user in response to interactive inputs.

Further, as described herein, the system may be configured and/ordesigned to generate user interface data useable for rendering thevarious interactive user interfaces described. The user interface datamay be used by the system, and/or another computer system, device,and/or software program (for example, a browser program), to render theinteractive user interfaces. The interactive user interfaces may bedisplayed on, for example, electronic displays (including, for example,touch-enabled displays).

Additionally, it has been noted that design of computer user interfaces“that are useable and easily learned by humans is a non-trivial problemfor software developers.” (Dillon, A. (2003) User Interface Design.MacMillan Encyclopedia of Cognitive Science, Vol. 4, London: MacMillan,453-458.) The various embodiments of interactive and dynamic userinterfaces of the present disclosure are the result of significantresearch, development, improvement, iteration, and testing. Thisnon-trivial development has resulted in the user interfaces describedherein which may provide significant cognitive and ergonomicefficiencies and advantages over previous systems. The interactive anddynamic user interfaces include improved human-computer interactionsthat may provide reduced mental workloads, improved decision-making,reduced work stress, and/or the like, for a user. For example, userinteraction with the interactive user interfaces described herein mayprovide an optimized display of time-varying report-related informationand may enable a user to more quickly access, navigate, assess, anddigest such information than previous systems.

Further, the interactive and dynamic user interfaces described hereinare enabled by innovations in efficient interactions between the userinterfaces and underlying systems and components. For example, disclosedherein are improved methods of receiving user inputs, translation anddelivery of those inputs to various system components, automatic anddynamic execution of complex processes in response to the inputdelivery, automatic interaction among various components and processesof the system, and automatic and dynamic updating of the userinterfaces. The interactions and presentation of data via theinteractive user interfaces described herein may accordingly providecognitive and ergonomic efficiencies and advantages over previoussystems.

Accordingly, various embodiments of the present disclosure may provideinteractive user interfaces for enabling non-technical users to quicklyand dynamically generate and edit complex reports including tables andcharts of data. The complex reports may be generated through automaticcalculation of applicable time intervals, access and traversal ofcomplex data structures, and calculation of output data based onproperty/attribute values of multiple nodes and/or edges within suchcomplex data structures, all in substantially real-time. The system mayeliminate the need for a skilled programmer to generate a customizeddata and/or a report. Rather, the system may enable an end-user tocustomize, generate, and interact with complex data in multiple contextsautomatically. Accordingly, embodiments of the present disclosure enabledata generation and interaction in fewer steps, result in fastergeneration of complex data, consume less processing and/or memoryresources than previous technology, permit users to have less knowledgeof programming languages and/or software development techniques, and/orallow less technical users or developers to create outputs (such astables and/or reports) than the previous user interfaces. Thus, in someembodiments, the systems and user interfaces described herein may bemore efficient as compared to previous systems and user interfaces.

According to an embodiment, a computer system is disclosed that isconfigured to access one or more electronic data sources in response toinputs received via an interactive user interface in order toautomatically calculate metrics based on a complex mathematical graphand insert the metrics into a dynamically generated table of theinteractive user interface, the computing system comprising: a computerprocessor; and a computer readable storage medium configured to: store acomplex mathematical graph comprising nodes and edges, each of the nodesstoring information associated with at least one of an account, anindividual, a legal entity, or a financial asset, each of the edgesstoring a relationship between two of the nodes, wherein a plurality ofattributes is associated with each of the nodes and each of the edges,wherein at least one of the nodes is associated with a time varyingattribute; and store program instructions configured for execution bythe computer processor in order to cause the computing system to:generate user interface data for rendering an interactive user interfaceon a computing device, the interactive user interface including: adynamically generated table including rows and columns, wherein each ofthe rows corresponds to a financial asset and its associated node or agroup of financial assets and its associated nodes, wherein each of thecolumns corresponds to a metric calculable with respect to each of thefinancial assets or groups of financial assets; and a context selectionelement including a listing of a plurality of perspectives from whichthe dynamically generated table may be automatically updated, each ofthe plurality of perspectives associated with a node of the complexmathematical graph; receive, via the interactive user interface, aselection of one of one of the plurality of perspectives; determine anode of the complex mathematical graph associated with the selectedperspective; automatically traverse the complex mathematical graph fromthe determined node so as to enumerate paths within the complexmathematical graph that are associated with the determined node; foreach enumerated path, determine any rows of the dynamically generatedtable associated with the enumerated path based on nodes commonlyassociated with the enumerated path and a row of the dynamicallygenerated table; generate a bucketing tree comprising value nodescorresponding to the rows of the dynamically generated table andassociated with the respective enumerated paths determined to beassociated with the rows; for each value node of the bucketing tree andeach metric of the dynamically generated table: determine one or moretime intervals associated with each of the enumerated paths associatedwith the value node, the one or more time intervals determined based onattributes associated with nodes of each of the enumerated pathsincluding any time varying attributes; determine one or more timeintervals associated with the metric; calculate, for each of theenumerated paths associated with the value node, one or more calculationintervals based on an intersection between the time intervals associatedwith the metric and the time intervals associated with the respectiveenumerated path; for each of the enumerated paths and each of thecalculation intervals associated with the respective enumerated paths:calculate an interval value corresponding to each calculation intervalbased on the metric; and aggregate the calculated interval valuesassociated with each of the enumerated paths to calculate a path valueassociated with each of the enumerated paths; and aggregate the pathvalues associated with each of the value nodes to calculate a metricvalue corresponding to each combination of value node and metric; andautomatically update the dynamically generated table with the calculatedmetric values, wherein each of the calculated metric values is insertedinto a cell of the table corresponding to the row associated with thevalue node associated with the calculated metric value and the columnassociated with the metric associated with the calculated metric value.

According to yet another embodiment, the interactive user interfacefurther includes an input element wherein the user inputs time varyingattribute information for association with a node via the input element,wherein the time varying attribute information includes at least twoattribute values and time intervals associated with each of the at leasttwo attribute values.

According to yet another embodiment, the rows of the dynamicallygenerated table are arranged hierarchically according to a user definedcategorization of one or more attributes associated with nodes of thecomplex mathematical graph.

According to yet another embodiment, the interactive user interfacefurther includes an input element wherein the user inputs thecategorization of the one or more attributes associated with nodes ofthe complex mathematical graph via the input element.

According to yet another embodiment, the interactive user interfacefurther includes a second input element wherein the user inputs one ormore metrics to be associated with the dynamically generated table viathe second input element.

According to yet another embodiment, the one or more metrics include atleast one of asset value, TWR, IRR, rate of return, cash flow, oraverage balance.

According to yet another embodiment, the interactive user interfacefurther includes a second context selection element wherein the userselects select a particular date, wherein the determined one or moretime intervals associated with the metric are based on the particulardate.

According to yet another embodiment, automatically traversing thecomplex mathematical graph comprises: traversing, from the determinednode, any edges and/or other nodes connected directly or indirectly withthe determined node; determining, based on the traversal, anynon-circular paths in the complex mathematical graph connected to thedetermined node; and designating the determined non-circular paths asthe enumerated paths associated with the designated node.

According to yet another embodiment, at least two edges of the complexmathematical graph are part of a circular reference from the designatednode back to the designated node, and wherein automatically traversingthe complex mathematical graph further comprises: determining whethertwo sequences of two or more traversed nodes are identical, and if so,backtracking the traversal and moving to the next adjacent node or edge.

According to yet another embodiment, each of the enumerated pathsinclude at least one node and at least one edge of the complexmathematical graph.

According to yet another embodiment, at least one column of thedynamically generated table corresponds to an asset value metric, andwherein calculating an interval value corresponding to each calculationinterval based on the asset value metric comprises determining amonetary value associated with the edges and/or nodes of the enumeratedpath for each calculation interval.

According to yet another embodiment, aggregating the calculated intervalvalues associated with each of the enumerated paths to calculate a pathvalue associated with each of the enumerated paths comprises summingeach of the calculated interval values.

According to yet another embodiment, the program instructions arefurther configured for execution by the computer processor in order tocause the computing system to, for each value node of the bucketing treeand each metric of the dynamically generated table: determine that nocalculation intervals are associated with a given enumerated pathassociated with the value node and a given metric; and automaticallyupdate the dynamically generated table so as to insert a blank spaceinto a cell of the table corresponding to the row associated with thevalue node and the column associated with the given metric.

BRIEF DESCRIPTION OF THE DRAWINGS

The following drawings and the associated descriptions are provided toillustrate embodiments of the present disclosure and do not limit thescope of the claims. Aspects and many of the attendant advantages ofthis disclosure will become more readily appreciated as the same becomebetter understood by reference to the following detailed description,when taken in conjunction with the accompanying drawings, wherein:

FIGS. 1A-1B illustrate example user interfaces of the system in whichdata is presented to the user in a table format.

FIG. 2A illustrates a computer system that may be used to implement anembodiment.

FIG. 2B illustrates a high-level view of a graph transformation.

FIG. 3A illustrates a process of generating a table view based on agraph representing a set of financial asset holdings.

FIG. 3B illustrates other steps in the process of FIG. 3A.

FIG. 4 illustrates an example of a graphical user interface for acomputer display unit.

FIG. 5 illustrates the display of FIG. 4 in which dropdown menu has beenselected and shows a plurality of named previously created views in alist.

FIG. 6 illustrates an example Edit Groupings dialog that displays a listof currently selected groupings and a tree representation of availablegroupings.

FIG. 7 illustrates an example Edit Columns dialog that displays a listof currently selected columns and a tree representation of availablecolumns.

FIG. 8 illustrates an example configuration dialog for a Factor.

FIG. 9A illustrates a home screen display illustrating a portfoliosummary view from the Perspective of Clients.

FIG. 9B illustrates another example in which widget and a Family optionhas been selected.

FIG. 9C illustrates an example of an Add TWR Factor dialog resultingfrom selecting the Edit Column dialog, selecting Performance Metricsfrom among the Available Columns, and adding TWR Factor as a column.

FIG. 10 illustrates the GUI of FIG. 4 after applying a Real Estatefilter.

FIG. 11 illustrates the GUI of FIG. 4, FIG. 10 in which vertical axislabel has been selected.

FIG. 12 illustrates an example in which some of the data in the tableview is selected.

FIG. 13 illustrates the display of FIG. 4 showing asset details.

FIG. 14 is a flowchart showing an example method of the system in whicha table is generated.

FIGS. 15A-15C illustrate an example traversal of a simplified graph.

FIG. 16 illustrates an example user interface including a tablegenerated as a result of the graph traversal of FIGS. 15A-15C.

FIG. 17A-17B illustrate an example bucketing tree and user interface ofthe system.

FIGS. 18A-18C illustrate example user interfaces of the system in whichthe user may associate a custom attribute with an asset.

FIGS. 19A-19B illustrate example manager attribute information that maybe associated with assets.

FIGS. 20A-20F illustrate example user interfaces of the system in whichdata is presented to the user in a table format based on associatedmanager attribute information.

FIGS. 21A-21C illustrate additional example user interfaces of thesystem in which data is presented to the user in a table format based onassociated manager attribute information.

FIG. 22A illustrates yet an additional example user interface of thesystem in which data is presented to the user in a table format based onassociated manager attribute information.

FIG. 22B illustrates calculation of time intervals based on attributeinformation associated with assets.

FIG. 22C is a flowchart showing an example method of the system in whichtime intervals associated with a given path and metric are calculated.

FIG. 23 is a flowchart showing an example method of the system in whicha table is generated, including time varying attributes.

FIGS. 24A-24E illustrate an example traversal of a simplified graph,including time varying attributes.

FIG. 25 illustrates a computer system with which various embodiments maybe implemented.

DETAILED DESCRIPTION

Although certain preferred embodiments and examples are disclosed below,inventive subject matter extends beyond the specifically disclosedembodiments to other alternative embodiments and/or uses and tomodifications and equivalents thereof. Thus, the scope of the claimsappended hereto is not limited by any of the particular embodimentsdescribed below. For example, in any method or process disclosed herein,the acts or operations of the method or process may be performed in anysuitable sequence and are not necessarily limited to any particulardisclosed sequence. Various operations may be described as multiplediscrete operations in turn, in a manner that may be helpful inunderstanding certain embodiments; however, the order of descriptionshould not be construed to imply that these operations are orderdependent. Additionally, the structures, systems, and/or devicesdescribed herein may be embodied as integrated components or as separatecomponents. For purposes of comparing various embodiments, certainaspects and advantages of these embodiments are described. Notnecessarily all such aspects or advantages are achieved by anyparticular embodiment. Thus, for example, various embodiments may becarried out in a manner that achieves or optimizes one advantage orgroup of advantages as taught herein without necessarily achieving otheraspects or advantages as may also be taught or suggested herein.

1.0 GENERAL OVERVIEW

As described above, embodiments of the present disclosure relate to acomputer system designed to provide interactive user interfaces forenabling non-technical users to quickly and dynamically generate, edit,and update complex reports including tables and charts of data. The userinterfaces are interactive such that a user may make selections, provideinputs, and/or manipulate outputs. In response to various user inputs,the system automatically accesses and traverses complex data structures(including, for example, a mathematical graph having nodes and edges,described below), calculates complex data based on the traversals, anddisplays the calculated complex data to the user. The displayed data maybe rapidly manipulated and automatically updated based on a contextselected by the user, and the system may automatically publish generatedata in multiple contexts.

The system described herein may be designed to perform various dataprocessing methods related to complex data structures, includingcreating and storing, in memory of the system (or another computersystem), a mathematical graph (also referred to herein simply as a“graph”) having nodes and edges. In some embodiments each of the nodesof the graph may represent any of (but not limited to) the following:financial assets, accounts in which one or more of the assets are held,individuals who own one or more of the assets, and/or legal entities whoown one or more of the assets. Further, the various data processingmethods, including traversals of the graph and calculation of complexdata, may include, for example: receiving and storing one or morebucketing factors and one or more column factors, traversing the graphand creating a list of a plurality of paths of nodes and edges in thegraph, applying the bucketing factors to the paths to result inassociating each set among a plurality of sets of the nodes with adifferent value node among a plurality of value nodes, and/or applyingthe column factors to the paths and the value nodes to result inassociating column result values with the value nodes. The system mayalso be designed to generate various user interface data useable forrendering interactive user interfaces, as described herein. For example,the system may generate user interface data for displaying of a tableview by forming rows based on the value nodes and forming columns basedon the column result values. Column result values may also be referredto herein as metrics.

Further, as described herein, the system may be configured and/ordesigned to generate user interface data useable for rendering thevarious interactive user interfaces described. The user interface datamay be used by the system, and/or another computer system, device,and/or software program (for example, a browser program), to render theinteractive user interfaces. The interactive user interfaces may bedisplayed on, for example, electronic displays (including, for example,touch-enabled displays).

FIGS. 1A-1B illustrate example user interfaces of the system in whichdata is presented to the user in a table format following a graphtraversal as described herein. Referring to FIG. 1A, the example userinterface includes two primary display portions 110 and 112. Within aright display portion 112 the user interface displays a table offinancial data associated with a particular individual, a group, or alegal entity. Specifically, the table displays a listing of financialassets associated with the particular individual, group, or legalentity, organized in a hierarchical fashion, as well as various metricsassociated with the listing. A left display portion 110 includes alisting of various clients and/or perspectives. As described in detailbelow, user interfaces of the system are, accordingly to someembodiments, generated with respect to a particular context. A contextmay include a perspective and/or a date. In some embodiments, theperspective identifies any of an individual, a group, and/or a legalentity, each of which may, in some embodiments, correspond to clients ofa user of the system. Accordingly, the display portion 110 includes alisting of various selectable perspectives (or clients), with aparticular client “Bob” 130 being selected (as indicated by a boxoutline).

The example user interface of FIG. 1A further includes a date selectionbox 114. As described, the context of the user interface may include adate which may be specified by the user via the date selection box 114(by, for example, direct input of a desired date and/or selection of adate in a dropdown list or calendar widget). The user interface mayfurther include a select view button 115, an edit table button 116,and/or an add filter button 118. In various embodiments, and asdescribed in further detail below, the user may select the select viewbutton 115 to specify particular types of tables, charts, or otherinformation to be displayed in the display portion 112; the user mayselect the edit table button 116 to specify an arrangement of data to bedisplayed in the table (or other chart and/or other informationdisplayed), types of data to be displayed in the table (or other chartand/or other information displayed), particular metrics to be displayedin the table (or other chart and/or other information displayed), and/orthe like; and the user may select the add filter button 118 to applyinformation filters to the table (or other chart and/or otherinformation displayed).

In various embodiments, any input from the user changing theperspective, changing the date, applying a filter, editing displayedinformation, and/or the like causes the system to automatically anddynamically re-traverse the graph and re-generate data to be displayedaccording to the user's inputs.

In the example user interface of FIG. 1A, the table displays variousinformation associated with the selected context (including theperspective, Bob, and the date, 2011-04-15), and based on other inputsfrom the user including a specification of two metrics (including acurrent value in column 114 and a value as of 2010-04-15 in column 146)and a particular hierarchical organization of information (as shown incolumn 142). Specifically, the table shows financial assets associatedwith Bob as of 2011-04-15, organized according to first, a manager ofthe financial assets, and second, a type of the financial assets.Further, metrics associated with the assets (and various groups of theassets) are displayed including a current value (for example, as of thedate of the current context 2011-04-15) and a value as of a specifieddate 2010-04-15. Column 142 shows each asset, including Security A andSecurity B, organized by a manager of the asset (in the example, bothSecurity A and Security B are managed by Henry) and a type of the asset(in the example, both Security A and Security B are of the type Equity).Columns 144 and 146 show metric values as of the current date (forexample, the date associated with the current context, 2011-04-15) and2010-04-15, respectively. As shown, between 2010-04-15 and 2011-04-15,the value of Security A owned by (or otherwise associated with) Bobincreased from $20,000 to $25,000, the value of Security B owned by (orotherwise associated with) Bob increased from $10,000 to $15,000, thevalue of all equities owned by (or otherwise associated with) Bobincreased from $30,000 to $40,000, the value of all assets managed byHenry that are owned by (or otherwise associated with) Bob increasedfrom $30,000 to $40,000, and the total value of all assets owned by (orotherwise associated with) Bob increased from $30,000 to $40,000.

According to some embodiments, the system may generate user interfacesthe provide the user with insights into data having time varyingattributes. For example, suppose that in the table of FIG. 1A, SecurityA is managed by Henry on the currently selected date, but was managed bya different manager at some earlier time. This fact is not representedin the table of FIG. 1A. Accordingly, the system provides, in someembodiments, that the user may specify that data is to be displayedtaking into account any associated time varying attributes (alsoreferred to herein as “historical values”). FIG. 1B shows, in thedisplay portion 112, an updated table of Bob's assets in which timevarying attributes are accounted for. In particular, in the table ofFIG. 1B, it is assumed that Security A was managed by Henry from2011-01-01 to 2011-12-31, and managed by Gary during all other times.Thus, the table of FIG. 1B includes rows corresponding to Security A asmanaged by Gary, and Security A as managed by Henry. Because Security Awas not managed by Gary during the current date (2011-04-15), no valueis displayed at location 152 of column 144. Likewise, because Security Awas not managed by Henry during the date associated with the metric ofcolumn 146 (2010-04-15), no value is displayed at location 154. However,values of metrics are displayed in the respective columns when the datesare applicable to the respective managers. For example, Security A had avalue of $20,000 on 2010-04-15, at which time it was managed by Gary,and a value of $25,000 on 2011-04-15, at which time it was managed byHenry. Note that Security B only appears under the Henry category asSecurity B was managed by Henry during both of the applicable dates(although it may have been managed by Gary or another manager during toother time period).

Accordingly, in various embodiments the system may calculate data (viacomplex graph traversal described herein) and provide a unique andcompact display of calculated data based on time varying attributesassociated with the calculated data. In an embodiment, the data may bedisplayed in a table, such as the example table of FIG. 1B, in whichdata is organized based on the time varying attributes and datesassociated with particular metrics specified by the user and/ordetermined by the system. In some embodiments, when no metric values areassociated with a particular item of data, a portion of the table isleft blank (as with the locations 152 and 154 of FIG. 1B) and/or omitted(for example, no row is shown for Security B under Gary in the table ofFIG. 1B as Security B is not associated with Gary during any time periodapplicable to the table).

In various embodiments the system may calculate time intervalsapplicable to calculations of various metrics. For example, in the userinterfaces of FIGS. 1A and 1B, the system calculates asset value metricsfor which a single date or time is applicable. In other examples, thesystem may calculate metrics that span periods of time such as a rate ofreturn of an asset over a number of years. Accordingly, the system maydetermine a set of time intervals associated with the metric, a set oftime intervals associated with applicable time varying attributes ofgraph data, and determine in intersection of the two sets of timeintervals. The calculated intersection of the sets of time intervals maythen be inputted into the complex graph traversal process to calculatemetric values for display in compact and efficient user interfaces ofthe system.

Advantageously, accordingly to various embodiments, the system maycalculate and provide, for example, any set of metrics with respect tograph having time varying attributes. The user may therefore easily findinsights that are not otherwise easily attainable. For example, thenon-technical user may easily compare asset returns by manager, whilethe managers of the assets change over time.

Accordingly, in various embodiments, large amounts of data areautomatically and dynamically calculated interactively in response touser inputs, and the calculated data is efficiently and compactlypresented to a user by the system. Thus, in some embodiments, the userinterfaces described herein are more efficient as compared to previoususer interfaces in which data is not dynamically updated and compactlyand efficiently presented to the user in response to interactive inputs.

In an embodiment, a method comprises creating and storing, in memory ofa computer, a graph having nodes and edges, wherein the nodes representfinancial assets and any one or more of: accounts in which one or moreof the assets are held, individuals who own one or more of the assets,or legal entities who own one or more of the assets; receiving, such asfrom a user of the computer, one or more bucketing factors and one ormore column factors; the computer traversing the graph and creating alist of a plurality of paths of nodes and edges in the graph; thecomputer applying the bucketing factors to the paths to result inassociating each set among a plurality of sets of the nodes with adifferent value node among a plurality of value nodes; the computerapplying the column factors to the paths and the value nodes to resultin associating column result values with the value nodes; creating andcausing display of a table view by forming rows based on the value nodesand forming columns based on the column result values.

In an embodiment, the method further comprises, for the bucketingfactors, selecting a particular bucketing factor; applying theparticular bucketing factor to the paths and receiving a bucketingresult value; creating a value node for the result value; associating,with the value node, all child nodes of the paths having bucketingresult values that match the value node.

In an embodiment, the method further comprises, for the column factors,for the value nodes, and for paths associated with a particular valuenode, applying a particular column factor to a particular path andreceiving a column result value; associating the column result valuewith the particular value node. In one feature, the edges represent anyone or more of: ownership; containment; or data flow. In another featureat least two of the edges comprise a circular reference from aparticular node to that particular node; further comprising determining,during the traversing, whether two sequences of two or more traversednodes are identical, and if so, backtracking the traversal and moving toa next adjacency. In yet another feature one or more of the bucketingfactors or column factors comprises an executable code segmentconfigured to perform one or more mathematical calculations using one ormore attributes of nodes in a path.

In still another feature one or more of the bucketing factors or columnfactors comprises an executable code segment configured to invoke afunction of a network resource using one or more attributes of nodes ina path.

In an embodiment, the method further comprises generating and causingdisplay of a graphical user interface comprising the table view and oneor more info-graphics, wherein each of the info-graphics isprogrammatically coupled to the table view using one or more datarelationships, and further comprising receiving user input selecting oneor more rows of the table view and, in response, automatically updatingthe info-graphics to display only graphical representations of the oneor more rows of the table view that are in the user input.

In an embodiment, the method further comprises generating and causingdisplay of a graphical user interface comprising the table view; causingdisplaying a bucketing factor menu identifying one or more availablebucketing factors; receiving a selection of a particular bucketingfactor; re-traversing the graph and applying the particular bucketingfactor to the paths to result in associating second sets of the nodeswith second value nodes among the plurality of value nodes; re-creatingand causing re-displaying an updated table view based on the secondvalue nodes and the column result values.

In an embodiment, the method further comprises generating and causingdisplay of a graphical user interface comprising the table view; causingdisplaying a column factor menu identifying one or more available columnfactors; receiving a selection of a particular column factor;re-traversing the graph and applying the particular column factor to thepaths and the value nodes to result in associating second column resultvalues with the value nodes; re-creating and causing re-displaying anupdated table view based on the value nodes and the second column resultvalues.

In an embodiment, the method further comprises generating and causingdisplay of a graphical user interface comprising the table view and oneor more info-graphics, wherein each of the one or more info-graphicscomprises one or more graphical elements that relate to one or moreassociated rows of the table view; receiving a selection of a particularone of the graphical elements; creating and storing a filter that isconfigured to pass only data in the table view that corresponds to theparticular one of the graphical elements; applying the filter to thetable view and causing re-displaying the table view using only data inthe table view that corresponds to the particular one of the graphicalelements.

In an embodiment, the method further comprises generating and causingdisplay of a graphical user interface comprising the table view and oneor more info-graphics, wherein each of the one or more info-graphicscomprises one or more graphical elements that relate to one or moreassociated rows of the table view; receiving a selection of a one ormore particular rows in the table view; updating the info-graphics bycausing displaying graphical elements corresponding only to theparticular rows in the table view.

In an embodiment, the method further comprises generating and causingdisplay of a graphical user interface comprising the table view and oneor more info-graphics; receiving a selection of one row associated withan asset; updating the graphical user interface to display a summary ofattributes of the asset, based on stored asset data or based onretrieving, at the time of the selection, the attributes of the assetfrom one or more global data sources.

In an embodiment, the method further comprises displaying, with thesummary of attributes of the asset, a transaction reference identifyinga number of transactions previously completed by a particularperspective.

In an embodiment, the method further comprises receiving and storing acontext comprising a perspective and/or a date, wherein the perspectiveidentifies any of an individual, a group, and a legal entity; beginningthe traversing at a first node associated with the perspective;receiving user input specifying a different perspective; repeating thetraversing beginning at a second node associated with the differentperspective and repeating the creating and causing displaying the tableview, based on updated value nodes and updated column result valuesyielded from the different perspective.

In an embodiment, the method further comprises receiving an updatedcontext comprising a changed date value; repeating the traversing,creating and causing displaying the table view based on updated valuenodes and updated column result values yielded from re-applying thecolumn factors using the changed date value.

2.0 STRUCTURAL AND FUNCTIONAL OVERVIEW

The computer system provides wealth management capabilities that enablenon-technical users to create new views, reports, and othermanipulations of a dataset without the need for custom programming.Custom views can be created in any user session by selecting particularcolumns, factors or metrics, ordering, filters providing groupings,graphics and other aspects of a desired view. The resulting views can besaved and reused in later sessions. However, a view that is needed onlyon a one-time basis also may be constructed rapidly using atomiccomponents without specialized programming knowledge. Further, views maybe shared with others such as team members, clients, or otherapplications. Sharing may include exporting to an application such as aspreadsheet, transferring to a report generator, or other mechanisms asfurther described herein.

FIG. 2A illustrates a computer system that may be used to implement anembodiment. The computer memory 200 stores a graph 202 that represents aset of investment holdings. In an embodiment, client or customerinvestment data is received from one or more sources, such asbrokerages, and transformed into position data prior to storage into adata repository for use by the system. Positions, in an embodiment, areconsidered the most fine-grained or atomic element of data manipulatedin the system rather than, for example, an account.

Memory 200 forms part of a computer system having a processor, massstorage, input-output devices, and other elements that are omitted inFIG. 2A for purposes of clarity. A view computation unit 206 can accessthe graph 202 for purposes of traversing the graph in response todifferent configuration data and generating output one or more tableviews 205 in the manner described further herein. View computation unit206 may be coupled to a rendering unit 207 for rendering andcommunicating table views 205 to any of a computer display unit 208 oran electronic document 211 of any form such as a report, spreadsheetfile, etc. In an embodiment, report unit 209 is configured to receiveview data from view computation unit 206, facilitate transfer of viewdata to pages of reports, and receive user input specifying metadata forreport formatting controls, as further described herein.

View computation unit 206 and graph 202 are implemented usingobject-oriented programming techniques in which nodes of the graph arerepresented using programmatic objects. For example, JAVA® may be used.

The foregoing elements of FIG. 2A may form part of a server computer 218that is coupled directly or indirectly through one or more computernetworks, represented by network 214, to a client computer 216. Network214 may comprise one or more LAN, WAN, or internetwork links and maycomprise the public internet through the use of appropriate protocolsfor ensuring data security, user authentication and user authorization.Client computer 216 may comprise an individual client computing devicesuch as personal computer, workstation, laptop, netbook, tabletcomputer, or smartphone that is coupled through a computer network tothe other elements of FIG. 2A. Client computer 216 hosts an internetbrowser program which, may be configured with virtual machine programexecution capability. For example, client computer 216 may host a JAVAvirtual machine and may receive and execute one or more JAVA files thatcause the browser to display a graphical user interface that receivesdata (for example, user interface data) from and facilitates interactionwith the server computer 218 and view computation unit 206.

View computation unit 206 also may be coupled to a custodian interfaceunit 213 that is coupled directly or indirectly through network 214 toan asset custodian computer 220. Asset custodian computer 220 serves asan authoritative source of data about accounts and asset positionsassociated with individuals or other entities represented in datarepository 204 and graph 202. Custodian interface unit 213 is configuredto obtain account and position snapshot data periodically or throughlive data feeds from asset custodian computer 220. Inbound data may betransformed from account-level data into position-level data and storedin data repository 204 or represented in graph 202 in memory for furtherreference and manipulation.

Embodiments may also interface in a similar manner to global datasources such as market data feeds that are independent of particularaccounts or positions but report current or historic market value ofassets or instruments. Examples of sources of global data includeThomson Reuters, New York Stock Exchange, NASDAQ, etc. In such anembodiment, global data sources may or may not override asset valuesthat are stored in the graph, based on configuration data. For example,a particular node of graph 202 representing an asset may store an assetvalue attribute that was obtained from positions data derived fromaccount data obtained from an asset custodian. However, if the asset is,for example, a market traded security, then a current intraday value forthe asset may be available from the global data source. Configurationdata may indicate whether global data source values for assets shouldoverride position data obtained from a custodian or other sources.

A set of investment holdings may be associated with an individual, alegal entity, or a group of individuals and/or legal entities such asone or more clients of an RIA firm. Graph 202 may be formed in memory200 based on data records obtained from data repository 204. Graph 202may comprise any number of nodes and edges, and the particular graphshown in FIG. 2A is provided solely to illustrate one example and not asa requirement or limitation.

Graph 202 may comprise nodes and edges having any level of complexity,and there is no requirement that nodes are organized in a hierarchicalarrangement; circular references may be represented. As an example,graph 202 comprises nodes for individuals named Beth and Ken who have anownership or trusteeship relationship to a Trust. The Trust is relatedto a company, Alpha Holdings LLC, which is also related to a secondcompany, Beta Holdings LLC that may own a Brokerage Account havinginstruments i1, i2, i3. Instruments i1, i2, i3 may represent stocks,bonds, options, or any other financial instrument that may be traded orreceive an investment; for purposes of illustrating a example, three (3)instruments are shown in FIG. 2A but practical embodiments may use anynumber of instruments. Beta Holdings LLC further has a relationship toKen and instrument i1 has a relationship to Beth; these relationshipscircle back within the graph and provide examples of non-hierarchicalnode-edge relationships. For example, one circular reference is the pathKen→Trust→Alpha Holdings LLC→Beta Holdings LLC→Ken.

The edges of the graph 202 may represent any type of relationship amongthe nodes connected by the edge. For example, the edges may representasset ownership relationships, liability relationships, equity ownershiprelationships, data flow relationships, and/or the like. Thus, forexample, one node may represent a security, another node may represent abrokerage account, and an edge connecting the two node may representthat the first node owns a particular number of shares of the secondnode.

As a further example, edge 210 may represent a flow of instrument datafrom a third party data source such as a brokerage data feed. Forexample, edge 210 could represent a brokerage data feed for instrumenti1 indicating that Beth owns 200 units, such as shares, having a valueof 25 per unit. Edge 210 may also represent an ownership relationshipseparate from value attributes. Edge 210 or other edges may representother concepts such as issuance of an asset; thus, one node mayrepresent an issuer of an asset, another node may represent the asset,and an edge connecting the two nodes may represent that the first nodeissued the second node.

Graph nodes may receive data for attributes of the nodes from acustodian, from a global data source, or from other data in the datarepository. For example, processing a particular client's custodialaccount may enable populating the graph 202 with some, but not all,values of attributes that are defined in the graph model. In anembodiment, view computation unit 206 is configured to investigatealternative data sources to supply missing node attribute values whenall attribute values are not available from a custodian. For example, aparticular global data source may have a sector attribute value that thecustodian does not have, and if so, the substitute value indicatingsector may be added to a node attribute. As another example, if datapreviously received from a custodian is determined to be stale, thenupdated data could be requested from one of the global data sources.

Further, overriding prior values is made straightforward through therepresentation of ownership relationships in graph edges, whereas nodesrepresent assets per se, possibly with value attributes. Consequently,modifying a value attribute of an asset node, based on receivedmarket-based values, enables the received values to affect allcalculations that reference the asset node. Other asset node attributesmay propagate in a similar manner. For example, if a particular RIA usermodifies an asset node representing ALPHA COMPANY to add an earningsreport document as an attribute, all clients of that particular user whoown positions in ALPHA COMPANY obtain access to the earnings reportthrough principles of object inheritance.

View computation unit 206 is configured to transform graph 202 into oneor more table views, graphs, charts, and other output. Tables, charts,graphs, and other components that may be inserted into user interfacesand/or reports of the present disclosure may be referred to herein aselements, report elements, or in some instances widgets. For purposes ofillustrating the example embodiments which follow, FIG. 4 illustrates anexample of a graphical user interface for a computer display unit. In anembodiment, the elements of FIG. 2A and the output of FIG. 4 areimplemented using the ADDEPAR computer software system commerciallyavailable from Addepar, Inc., Mountain View, Calif.

FIG. 4 illustrates a view of holdings from the perspective of anindividual named Uncle Moneypenny as indicated by Perspective label 402.A Portfolio tab 404 indicates that the user is viewing a portfolio ofholdings of Moneypenny. A Filters region 406 indicates that no datadisplay filters are presently applied to change a view of the data inthe GUI. Selecting an Add link in the Filters region causes viewcomputation unit 206 to display a GUI widget that may receivedefinitions of filters, as further described herein.

FIG. 4 comprises a table view 408 which, for purposes of illustrating aexample, comprises rows organized by asset class as indicated by anAsset Class bucketing label 410 and columns showing asset class name andcurrent value as indicated by column label 412. Assets within AssetClass 410 are organized in a hierarchy or tree in which boldface labels408A indicate an asset class bucket and non-bold labels 408B indicateindividual assets within the associated asset class bucket.

Selecting an Edit Groupings widget 414 causes view computation unit 206to display a GUI dialog that may receive reconfiguration of data valuesthat determine the identity and order of buckets and therefore theparticular manner of displays of rows of the table view 408.

FIG. 6 illustrates an example Edit Groupings dialog 602 that displays alist of currently selected groupings 606 and a tree representation ofavailable groupings 604. A comparison of selected groupings 606 to FIG.4 will show that the selected groupings of FIG. 6 are represented inFIG. 4. User selection of a remove (−) icon in the selected groupings606 causes the view computation unit 206 to remove the selected groupingfrom selected groupings 606; subsequent selection of OK widget 610 indialog 602 causes view computation unit 206 to close the dialog andre-display the table view 408 without the removed grouping. Userselection of open (+) and close (−) icons in the tree display ofavailable groupings 604 causes categories of groupings to open untilleaf nodes of the tree are shown. For example, in FIG. 6 the user hasselected open icons for Asset Class Specific and Options, yielding alist of available option groupings 608.

Selecting an add (+) icon associated with any of the available optiongroupings 608 causes view computation unit 206 to add the selectedoption grouping to selected groupings 606; subsequent selection of OK indialog 602 causes view computation unit 206 to close the dialog andre-display the table view 408 with the added grouping. For somegroupings, selecting the add (+) icon causes view computation unit 206to display a Factor details dialog that prompts the user to enter orconfirm one or more configuration values associated with a Factor thatdrives the grouping. FIG. 8 illustrates an example configuration dialogfor a Factor. For example, assume that a user selects, from AvailableGroupings, Holding Details and then % of Portfolio. In response, viewcomputation unit 206 causes displaying dialog 802, which comprises aTime Point widget 804 and Portfolio Fraction widget 806 that prompt theuser to select one of several available values using drop-down menus.Alternatively, the user may select Favorites drop-down menu 808, whichassociates labeled menu items with stored values for Time Point andPortfolio Fraction. Selecting the OK widget 810 causes view computationunit 206 to close the dialog and store the specified values for TimePoint and Portfolio Fraction in association with the % of PortfolioFactor, for use in subsequent computations. Thus, the system providesextensive opportunities for flexible customization by specifying thedesired basis for computation, without requiring custom programming ofalgorithms or methods for particular factor computations.

Referring again to FIG. 6, a search box 612 may receive user input ofkeywords associated with groupings and causes view computation unit 206to update available option groupings 608 with values that match thekeywords.

Referring again to FIG. 4, selecting an Edit Columns widget 416 causesview computation unit 206 to display a GUI widget that may receivereconfiguration of data values that determine the identity and order ofcolumns of the table view 408. FIG. 7 illustrates an example EditColumns dialog 702 that displays a list of currently selected columns706 and a tree representation of available columns 704. A comparison ofselected columns 706 to FIG. 4 will show that the selected columns ofFIG. 7 are represented in FIG. 4. User selection of a remove (−) icon inthe selected columns 706 causes the view computation unit 206 to removethe selected column from selected columns 706; subsequent selection ofOK widget 710 in dialog 702 causes view computation unit 206 to closethe dialog and re-display the table view 408 without the removed column.User selection of open (+) and close (−) icons in the tree display ofavailable columns 704 causes categories of columns to open until leafnodes of the tree are shown. For example, in FIG. 7 the user hasselected open icons for Holding Details, yielding a list of availableoption columns 708.

Selecting an add (+) icon associated with any of the available optioncolumns 708 causes view computation unit 206 to add the selected optioncolumn to selected columns 706; subsequent selection of OK in dialog 702causes view computation unit 206 to close the dialog and re-display thetable view 408 with the added grouping. In some cases, selecting the addicon may cause the view computation unit 206 to display a dialog of thekind shown in FIG. 8 for groupings, with configuration parameter valuesapplicable to the particular selected column. A search box 712 mayreceive user input of keywords associated with columns and causes viewcomputation unit 206 to update available option columns 708 with valuesthat match the keywords.

The GUI of FIG. 4 further comprises a Select View dropdown menu 422 thatmay be used to select and apply different views that have beenpreviously created and saved by others. For example, in FIG. 4 the GUIcomprises a table view 408 and one or more info-graphics such ascategorization pie chart 418, and bar chart 420. As an example, tableview 408 reflects an ownership breakdown by asset class and value; otherview selections may cause view computation unit 206 to display differentcombinations of buckets and columns, tables, charts and graphs. In FIG.4 and other drawing figures herein, the info-graphics comprise a piechart and a bar chart, solely to illustrate examples; however, in anembodiment, the GUI of FIG. 4 comprises two or more info-graphic optionicons 430 indicating the availability of a table view, pie chart, barchart, or line graph. Other embodiments may support info-graphics ofother types. View computation unit 206 is configured to receive userinput selecting one of the info-graphic option icons 430 and, inresponse, to change the info-graphic panel adjacent to the selectedoption icon to a different form of info-graphic. For example when piechart 418 is displayed, selecting a line graph icon from among optionicons 430 causes view computation unit to display a line graph in placeof the pie chart and using the same underlying data as a basis for theline graph.

In an embodiment, icons 430 include an asset details icon that maytrigger display of detailed information about a particular asset thathas been selected in the table view 408. FIG. 13 illustrates the displayof FIG. 4 showing asset details. In the example of FIG. 13, in tableview 408 one asset 1302 is selected as indicated by a checkbox in therow of the selected asset, and asset details icon 1301 has beenselected. View computation unit 206 is configured, in response to aselection of the asset details icon 1301, to cause displaying in theinfo-graphics area of the display, an asset details panel 1304comprising a summary sub-panel 1306, owner sub-panel 1308, andattachments sub-panel 1310. In an embodiment, summary sub-panel 1306lists attributes pertaining to the selected asset, which viewcomputation unit 206 may obtain by retrieving from data repository 204.Owner sub-panel 1308 specifies one or more owners of the selected asset;the owners are those individuals, clients or legal entities that areassociated with the current logged in user of the system. For example,when the user is an RIA, the Owner sub-panel 1308 may identify allclients of that user who have a position in the selected asset. Ownersub-panel 1308 further comprises a selectable hyperlink label indicatingthe number of transactions that each owner has completed for theselected asset; in the example of FIG. 13, “1 Transaction” is indicated.View computation unit 206 is configured, in response to selection of thehyperlink label, to retrieve information describing the transactions ofthat owner and display transaction detail in a pop-up menu.Consequently, a user is able to rapidly obtain transaction data forassets of clients or legal whose holdings are represented in the system,from within a display that has extensive viewing capabilities.

FIG. 5 illustrates the display of FIG. 4 in which dropdown menu 422 hasbeen selected and shows a plurality of named previously created views ina list 423. Selecting any particular view from list 423 causes viewcomputation unit 206 to replace table view 408 with a new view based onthe bucket Factors and column Factors that were defined for the selectedview, and to update pie chart 418 and bar chart 420 based on the data inthe new view. Replacement of the view involves re-computing the viewbased on the bucket Factors, column Factors and current Perspective ofMoneypenny, in the manner described further herein. In some embodiments,pie chart 418 and bar chart 420 are replaced with different graphicalviews of data or removed completely.

In an embodiment, each of the info-graphics such as pie chart 418 andbar chart 420, by default, display charts and graphs based on the datathat is then currently shown in table view 408. However, in anembodiment, view computation unit 206 is configured to respond to aselection of any of the info-graphics by updating the table view 408.

In an embodiment, the GUI of FIG. 4 further comprises an Export widget424 which, when selected, begins operation of a report and data exportfunction, as further described herein.

Embodiments operate in part based upon stored data representing aContext of a particular view of the graph 202. In an embodiment, aContext comprises a Perspective and/or a Date (or date range, alsoreferred to herein as a time period). A Perspective indicates anindividual, legal entity, or group and a Date indicates a time point atpresent or in the past. For example, a view of graph 202 from thePerspective of Ken may be different than a view generated from thePerspective of Beth. In an embodiment, a Perspective may comprise two ormore individuals, such as a husband and wife, groups, or multiple legalentities. A change in Perspective results in a change in calculations ofvalues of assets, in many cases. For example, the value of an asset froma particular Perspective typically depends upon the percentage ofownership of a particular person or legal entity. As an example basedupon graph 202, the percentage of ownership in Beta Holdings LLC may bequite different for Beth and for Alpha Holdings LLC because of thepresence or lack of intervening individuals or legal entities withdifferent ownership arrangements, shares or percentages.

Graph 202 may be represented in a backing store such as a relationaldatabase system, represented in FIG. 2A by data repository 204. In anembodiment, each node in graph 202 is a row in a table in the database.An Edges table identifies edges in graph 202 in terms of identifiers ofnodes from which an edge begins and to which an edge connects (FromID,ToID). In an embodiment, during operation all rows from the database areloaded into main memory and organized in a graph representation inmemory for use during a user session. In an embodiment, view computationunit 206 interacts with graph model logic 212 to implement a graph modeland perform graph manipulation operations; in various embodiments, thegraph model logic may comprise custom code or may be based on anopen-source project such as Tinkerbell.

Embodiments also apply one or more Factors as part of generating views.In an embodiment, a Factor may be any recognized financial metric. AFactor, for example, may be internal rate of return (IRR). A Factor is acomputational unit that receives, as input, a path from a graph such asgraph 202 and a Context.

For a table view, each Factor may be used as either a bucketing Factoror a column Factor. An example of a bucketing Factor is asset class, andan example of a column Factor is value. Based on such a configuration,an output table view would comprise rows identifying asset classes and avalue for each asset class. The configuration of asset class as abucketing Factor and value as a column Factor causes the viewcomputation unit 206 to compute values by traversing graph 202 andconsolidating values in terms of asset classes. In an embodiment,configuring a column Factor may be accomplished by selecting a userinterface widget and selecting a Factor from a drop-down list. Selectingan additional column Factor causes view computation unit 206 tore-compute the table view by again traversing graph 202. For example, ifIRR is configured as a column Factor, and rows in the table viewrepresent Instruments, then the table view will comprise a column thatshows an IRR value for each Instrument.

Further, selecting a second bucketing Factor causes the view computationunit 206 to re-compute the table view by consolidating values in termsof the second bucketing Factor; the resulting table view is displayedhierarchically so that multiple bucketing Factors are nested. Forexample, these techniques allow generating a table view that displaysassets by asset class, then by owner, etc. In an embodiment, a user mayre-order the bucketing Factors within a graphical list of all selectedbucketing Factors, and the re-ordering causes the view computation unit206 to re-compute and re-display the table view using a differenthierarchy of bucketing Factors based on the re-ordered list of bucketingFactors.

3.0 GENERATING TABLE VIEWS FROM GRAPHS

To display a view of the data in graph 202 in a form that is familiar tothe typical user, the graph is transformed into a table view consistingof rows and columns for display in a graphical display of a computerdisplay unit. FIG. 2B illustrates a high-level view of a transformation.In general, a graph 202 and a Context 252 are received as input to agraph-table transformation 254, which generates an output view 256. Theoutput view 256 may comprise a table, chart, or other output that isvisually perceivable at a graphical display unit.

FIG. 3A illustrates a process of generating a table view based on agraph representing a set of financial asset holdings. In an embodiment,a view of data in a particular Context is created bycomputer-implemented processes that walk graph 202, creating and storinga plurality of paths within the graph. In block 302, the graph istraversed and a plurality of paths through the graph are stored in apath list 304. Traversal may use recursive transition techniques andeither depth-first or width-first traversal is workable. In anembodiment, the graph is traversed starting at a source node asspecified by the Perspective of the Context. For example, assume thatthe Perspective is Ken; graph traversal begins at the Ken node and thepath list 304 would contain:

-   -   [Ken]    -   [Ken, Trust]    -   [Ken, Trust, Alpha Holdings LLC]    -   [Ken, Trust, Alpha Holdings LLC, Beta Holdings LLC]    -   [Ken, Trust, Alpha Holdings LLC, Beta Holdings LLC, Brokerage        Account] and so forth.

Changing the Context causes the view computation unit 206 to re-computea set of paths from the changed Perspective or Date represented in thechanged Context. For example, if a user during a single session changesfrom Ken to Beth, any and all displayed table views would re-compute andwould be redisplayed, illustrating holdings from the Perspective ofBeth. The Perspective also could be for Trust, causing the viewcomputation unit 206 to re-display a table view illustrating values fromthe point of view of the Trust without regard to what percentages areowned by particular human individuals.

Because the same processes described herein are re-performed based on adifferent root node as indicated by the Perspective, the processesherein offer the benefit of rapid generation of completely differentasset value and holdings displays even when the newly selectedPerspective is unrelated to a prior Perspective. Further, users havecomplete flexibility in how to display asset holdings and customprogramming is not required to obtain displays that reflect differentroll-ups or different user ownership regimes.

For example, FIG. 9A illustrates a home screen display 902 illustratinga portfolio summary view from the Perspective of Clients. In anembodiment, display 902 comprises a view type pull-down widget 904which, when selected, displays a list of available views. Selecting aNew widget 906 opens a dialog in which a user may specify configurationvalues for a new Person or Group, which then can be referenced in views.In the case of a Clients view, screen display 902 comprises a Clientcolumn 908 that identifies a person, a Current Value column thatidentifies aggregate current value of all holdings of that client, and aLast Viewed column that indicates the last time that the current userviewed the data.

FIG. 9B illustrates another example in which widget 904 and a Familyoption has been selected. In response, view computation unit 206 hasre-traversed the graph 202 and consolidated values based on familymembership; to support such a view, family relationships are representedin graph 202, for example using edges labeled as family relationships toconnect nodes of various individuals. In the example of FIG. 9B, theview comprises a Family column 920 and Current Value column 922, whichare the only columns defined for the Family view. Selecting an open (+)widget for a particular Family causes the view computation unit 206 todisplay child nodes of the named family and Current Value totals for thechild nodes. Similar views may be generated for legal entities such astrusts. A view of Current Value for a legal entity such as a trust isgiven from the trust's perspective and will indicate total value of allknown assets, even if the current user (for example, a particularfinancial advisor) only works with one individual who owns a minoritystake in the trust.

The example of FIG. 2A includes circular references, and FIG. 3Aimplements logic to prevent block 302 from causing an infinite loop,while permitting accurate representation of the value of assets bypermitting edges to loop back once. In particular, FIG. 3A incorporateslogic that permits a cycle to occur only once. In an embodiment, atblock 306, a sequence of already traversed nodes is periodically checkedand in block 308 the process tests whether two identical sequences areadjacent. For example, if nodes are labeled with alphabetic characterlabels, then the traversal sequence ABCAB is considered valid, but thesequence ABCABC is invalid. Although the first sequence includes twoinstances of path Aft the instances are not adjacent; however, in thesecond sequence, two instances of path ABC are adjacent and thereforeinvalid. Referring again to FIG. 2A, the sequence [Ken, Trust, AlphaHoldings LLC, Beta Holdings LLC, Ken, Alpha Holdings LLC] is valid, but[Ken, Trust, Alpha Holdings LLC, Beta Holdings LLC, Ken, Trust, AlphaHoldings LLC, Beta Holdings LLC] is invalid.

In block 310, upon detecting an invalid identical adjacent sequence, theprocess backtracks the recursive walk of the graph by one node and movesto the next adjacency. In effect the process adjusts internal recursionsteps to avoid re-traversing a second identical sequence. Traversalcontinues until all nodes, edges and adjacencies have been traversed, asrepresented in the test of block 312. Upon completion, path list 304 isfully populated with all valid paths through the graph.

At block 314, a bucketing process is performed to form nodes in thepaths into a tree (also referred to herein as a “bucketing tree”) orother hierarchy of buckets as specified by the then-currentconfiguration of bucketing Factors 315. Referring now to FIG. 3B, atblock 316, a root node (also referred to herein as a “root value node”and/or a “root node” of the bucketing tree) for the tree is created inmemory and initially all paths in the path list 304 are associated withthe root node. At block 318, a bucketing Factor is selected, and block318 forms a loop with block 330 that iterates through all configuredbucketing Factors. For example the first selected bucketing Factor couldbe asset class.

At block 320, the selected bucketing Factor is applied to all the pathsin the path list 304, resulting in generating a value for the bucketingFactor. The following pseudocode represents applying a factor in anembodiment:

-   -   for (path: paths) {        -   val=factor.apply (path)}    -   factor <T>    -   T apply (list <Path>, Context)

If the first selected bucketing Factor is asset class, then theresulting value val might be Stock, Bond, etc. At block 321, a node inthe tree hierarchy is created for the value; for example, a Stock nodeis created. At block 322, the process tests whether the current node(initially the root node) has a child node that matches the value. Thus,one test would be whether the root node has a Stock node as a childnode. If the result is YES, then the current path is associated with thevalue node that was created at block 321. For example, if the currentnode has an ALPHA COMPANY Stock node as a child, then the ALPHA COMPANYStock child node is associated with the Stock value node as shown atblock 324. If the result of the test at block 322 is NO, then at block326 a new node is created for the current path. Another example of thebucketing process is described below in reference to FIGS. 15A-15C.

In various embodiments, various filtering or correction processes may beapplied to improve the appearance or analytical value of the result ofbucketing. For example, certain bucketing Factors may return values thatare too granular to justify creating a new value node, so the returnvalues could be aggregated into a larger bucket. As a particularexample, if IRR is a bucketing Factor and returns a value of 1.2, theprocess could elect to associate that result with a “1.0 to 5.0” IRRbucket, and associated value node, rather than creating a new value nodejust for IRR results of 1.2.

In an embodiment, configuration data may define the range of values thatare included in a particular bucket, so that the nature of buckets maybe customized on a per-user or per-session basis. For example, assumethat a user wishes to classify stock assets as Large Cap, Mid Cap, SmallCap; different users may wish to define ranges of market capitalizationdifferently for each of the three (3) classifications. In an embodiment,graphical user interface widgets may be selected to identify particularbucketing Factor values and the ranges of result values that eachbucketing Factor should yield. Further, in an embodiment, any user maycreate any other desired new bucketing Factor by configuring a genericbucketing Factor to trigger on the presence of a particular metadatavalue in a particular asset or node. For example, a user could create aHedge Fund Strategy (Quant) bucketing Factor that will classify assetsinto a node, ultimately causing reporting them as a row in a table view,when the value of a Hedge Fund Strategy metadata attribute of an assetis Quant.

Iterating to another bucketing Factor by transferring control from block330 to block 318 results in re-processing path list 304 for a differentbucketing Factor, for example, Country.

When all paths have been processed in the steps preceding block 330 forall configured bucketing Factors, the result is a set of nodes,representing each bucketing Factor, each having associated therewith allpaths to nodes that match the value yielded by applying the bucketingFactor to a path. The effect is that each node representing a bucketingFactor has associated with it all matching paths and nodes in the graph202. For example, if path list 304 comprises 100 paths, then a firstbucketing Factor node for Stocks might have 50 paths, a Bonds node mighthave 40 paths, and a Commodities node might have 10 paths.

The association of paths with a bucketing Factor node, as opposed toindividual assets or terminal nodes that represent assets provides adistinct difference as compared to other systems and provides specialbenefits for various other features of the systems as further described.For example, a particular Perspective, such as Ken or Beth, may havemultiple paths to the same ultimate asset. The present system providesways to consolidate or roll-up multiple different paths into a singlevalue for a particular asset, regardless of the number, complexity ordirection of the paths. For other features and reasons, the paths alsomatter, as subsequent description will make clear.

At block 331, the process of FIG. 3B performs column processing usingeach value node in the tree that was created and associated with pathsin preceding steps. As shown at block 331, all configured column Factorsare processed and block 331 represents starting an iteration ofsubsequent block for all such configured column Factors.

As indicated in block 332, for a particular column Factor, all valuenodes are considered iteratively; further, block 334 representsiterating through all paths in a particular value node. For each suchpath, at block 336, a particular column Factor is applied to the currentpath, resulting in a value; as noted above, a Factor receives one ormore paths and a Context as input, both of which are known and availableat block 336. The same pseudocode as provided above may be used.

The resulting value is associated with the current value node at block338. As shown in block 340, when all paths for a particular value nodehave been processed, the sum of all values that have been associatedwith the value node may be returned as a column value (also referred toherein as a “column result value” and/or a metric) for display orinclusion in a table view for a row associated with the value node.Processing continues iteratively until all column Factors have resultedin generating values for all columns of that row or value node.

Each column Factor may define a complex calculation by overriding amethod in a class definition for a generic column Factor. For example, aFactor may call an ownership determination method to determine apercentage of ownership represented in a path as a precursor tocomputing a value of an asset. A Factor may call another Factor toperform such a computation. For example, a value Factor may call apercent-ownership Factor, which in turn could perform a matrixmultiplication to determine percent ownership, and the value Factor maymultiple the resulting percentage value by a current value of an assetto determine a particular Perspective's value for the asset.

Factors may implement complex logic for concepts such as internal rateof return. For example, a Factor may compute a date on which Beth becamea trustee of the Trust, determine values of all transactions thatoccurred on or after that date, separately call a value Factor todetermine a current-day value of each asset involved in each suchtransaction, etc.

In various embodiments, control steps may be performed in the processesof FIG. 3A, FIG. 3B to improve the quality of display. For example, if aFactor returns a result of “unknown value,” the resulting column valuemay need to be modified or removed for a particular value node, sincethe user cannot gain any added information from an unknown column. Theresult would be that a particular section of a table view or treerepresented in the table view would have blank column values.

Embodiments facilitate the ability to perform multi-currency displaysand calculations so that values in multiple currencies are concurrentlydisplayed in the same table view. For example, the Edit Columns dialogmay be used to select a Value factor, and add it as a column to a tableview, that is expressed in any of a plurality of currencies or in aNative Currency, which is the currency in which the underlying asset isactually held or tracked by a custodian. Any number of such columns maybe added to a particular table view by repeatedly selecting the EditColumns dialog, adding the Value factor with different currency values,and applying the selection to the view.

Embodiments provide the ability to display views of asset values formultiple different time periods in different columns within the sameview. FIG. 9C illustrates an example of an Add TWR Factor dialog 930resulting from selecting the Edit Column dialog, selecting PerformanceMetrics from among the Available Columns, and adding TWR Factor as acolumn. (TWR refers to Time Weighted Rate of Return.) In response, theview computation unit 206 causes displaying an Add TWR Factor comprisinga Period drop-down menu 932 having a list 934 presenting a plurality oftime period options. For example, for a particular view a user may add acolumn for TWR based on a Trailing Period, Calendar Period, Static DatePeriod, Since Inception Date, Current Period, or Custom Period. For someoptions the user is expected to enter time quantity and term valuesusing time widgets 936. When the configuration values of dialog 930 areapplied to a view, applying the TWR Factor to a traversal of the graph202 will result in performing calculations based on available historicalasset data for the time periods as specified. A user may add multipleTWR Factor columns to a particular view, each column having a differentPeriod configuration, for example, to permit comparison of assetperformance to benchmarks using different metrics of interest.

Changing the Date associated with the Context does not necessarilyaffect all date periods for the TWR Factor or other factors in the samemanner. For example assume that the foregoing TWR Factor columns havebeen configured, that the current date is March 30, and then the userchanges the Date associated with the Context to be March 1. The TWRFactor that is based upon a 1-year trailing date would then computevalues based on March 1 and 1 year earlier. A TWR Factor that is basedon a Start Date and End Date would use March 1 as the new Start Date butthe End Date would be unchanged. A Factor that is based on a static datewould be unaffected. Thus, the system offers the capability toindependently control each column of a table view based on configurationdata. Further, modification of date values in this manner enables a userto preview the impact of the change on output data that may be usedlater in a report.

Filters may be used to further customize the appearance or content of atable. A filter is a computational unit, such as a programmatic object,that determines whether edges and nodes in one or more paths should bereflected in output data in a table view. Filters are applied to pathsusing the processes described above, on a per-path basis. Thus, creatingand applying a filter causes view computation unit 206 to re-traverseall paths of the current view and to apply the filter during pathtraversal; this approach contrasts sharply with approaches of others inwhich filtering is merely applied to an output table or to a datasetthat has been retrieved from a database. Further, filters may be appliedto entities that are not visualized in a particular table view. Forexample, a view may be filtered to show the top 10 holdings based onIRR, even though IRR is not present in the table view.

Filters may be created through manual user selection and action byselecting the Filters Add (+) icon and responding to a filter creationdialog, or semi-automatically by selecting elements of info-graphics. Inan embodiment, info-graphics such as charts 418, 420 are configured withhyperlinks that cause the view computation unit 206 to create a filterand apply the filter to the table view 408. FIG. 10 illustrates the GUIof FIG. 4 after applying a Real Estate filter. In an embodiment, a usermay select any pie wedge in the pie chart 418, or any bar in the barchart 420, to cause creating a filter. In the example of FIG. 10, theuser selected the Real Estate wedge 1001 of the pie chart 418 in thedisplay of FIG. 4; in response, view computation unit created a filter1004 as seen in the filter region and applied the filter to the tableview to result in displaying only real estate assets. Further, thefilter is concurrently applied to both the info-graphics with the resultthat the pie chart displays a single solid circle since 100% of theassets listed in the table view are real estate assets. The filter 1004may be removed by hovering a cursor over the filter and selecting aremove (X) icon. The same form of filter control may be activated byselecting a bar of the bar chart 420.

Conversely, if the filter region of the table view is used to define oneor more filters, then the info-graphics automatically update to reflectthe filters that have been newly applied.

In an embodiment, the same basic processes described above forgenerating table views may be applied to generating the pie chart 418and bar chart 420. For example, the X axis of the bar chart 420 may bedefined using a bucket Factor and the Y axis may be defined using acolumn Factor. For example, a bar chart may be defined by bucketing IRRon the X axis while particular values are determined using column Factorvalue generating techniques as described above for table views.

In an embodiment, bar graph 420 comprises a vertical axis label 1006 andhorizontal axis label 1008 that are configured as selectable hyperlinks.View computation unit 206 is configured to cause displaying, in responseto user selection of an axis label 1006, 1008, a pop-up menu listingavailable Factors that may be selected for use as axes. FIG. 11illustrates the GUI of FIG. 4, FIG. 10 in which vertical axis label 1006has been selected. View computation unit 206 is configured to causedisplaying pop-up menu 1102 comprising a list 1104 of available Factorsthat may be selected as the basis of computing a new vertical axis forthe bar graph 420. A user may scroll through list 1104 and select anyFactor of interest, or type keywords for a Factor name in search box1106 to receive a list of matching Factors. Selecting a Factor from list1104 causes view computation unit 206 to cause closing the menu 1102 andrecomputed the chart 420 using the newly selected Factor. A differentFactor for the X-axis may be applied in a similar manner by selectinghorizontal axis label 1008 and selecting a new Factor from a pop-upmenu.

In an embodiment, Factors include value by any of a large plurality ofcurrencies. Consequently, a user or analyst may view values by currencyaccording to currency rates and conversions of the present day, withimmediate recalculation by re-traversing the graph.

In an embodiment, view computation unit 206 is configured to re-computeand cause re-displaying info-graphics such as pie chart 418 and barchart 420 based on changes in selections to data in table view 408. FIG.12 illustrates an example in which some of the data in the table view isselected. In screen display 1202 of FIG. 12, table view 408 comprises afirst set of rows 1204 and a second set of rows 1206 indicating assetsorganized by asset class. The first set of rows 1204 has been selectedas indicated by checks in selection checkboxes 1230 while the second set1206 is not selected as indicated by non-checked selection checkboxes1208. In an embodiment, a range of rows may be selected by individuallychecking checkboxes 1230, 1208 or by selecting one row and then usingkeyboard control combinations such as SHIFT-click or CTRL-click toselect a range of rows or multiple discrete rows. View computation unit206 is configured to re-compute and cause re-displaying pie chart 1218and bar chart 1220 to reflect only the selected rows and omit dataassociated with non-selected rows. For example in FIG. 12 it will beseen that pie chart 1218 comprises only three (3) wedges for Cash & CashEquivalents, Equity, and Equestrian assets because the first set 1204 ofrows comprises only assets in those asset classes. The sum of assetsrepresented in the pie chart 1218 is the sum of only the first set 1204of selected rows. Similarly, bar chart 1220 has been re-computed andredisplayed to reflect only the Sectors represented in the first set1204 of selected rows.

In an embodiment, view computation unit 206 is configured to save a viewof the type shown in FIG. 4, FIG. 5, FIG. 10, FIG. 11, FIG. 12 inresponse to user input requesting to save a view. In one embodiment,referring again to FIG. 4, a user may select the Select View menu 422 tocause displaying a list of named, previously saved views; one menuoption is Save As. In response to receiving a selection of Save As inmenu 422, view computation unit 206 is configured to cause displaying adialog that prompts the user to enter a name for the current view. Inresponse to receiving user input specifying a name, the view is saved indata repository 204 in the form of a named set of metadata defining theview. Example metadata that define a view include the Context, theFilters applicable to the view, the grouping and column Factors definingtable view 408, and the Factors defining axes of the chart 420.

After a view is saved, a user may retrieve and use the view with anyother Context. For example, the same user could change the Context to adifferent client or legal entity, and the view computation unit 206 isconfigured to apply, in response, the metadata defining the view toportions of the graph that relate to the newly selected client or legalentity. As a result, table view 408 and related info-graphics arere-computed and redisplayed to reflect holdings of the newly selectedclient or legal entity.

In an embodiment, when a user logs out and logs back in again in a lateruser session, the last saved view from the prior user session is used asthe first view that is displayed in the new user session.

4.0 EXPORTING VIEWS AND GENERATING REPORTS AND PUBLICATIONS

In an embodiment, view computation unit 206 is configured to export datashown in views to other applications or to other document formats suchas MICROSOFT EXCEL or ADOBE PDF. In an embodiment, view computation unit206 is configured to perform export operations based on the currentview. For example, in one embodiment, exporting is initiated by a userselecting the Export widget 424. In response, view computation unit 206causes highlighting all of the table view 408 and current info-graphicssuch as pie chart 418 and bar chart 420, and causes displaying, in eachof the table view and info-graphics, a selectable icon representing anavailable export format for that area of the display. For example, viewcomputation unit 206 may cause displaying an EXCEL icon and a PDF iconover the table view 408, but may display only a PDF icon over pie chart418 and bar chart 420 since info-graphics of those forms cannot beexported in the form of an EXCEL table.

In an embodiment, view computation unit 206 is configured, in responseto selection of one of the ADOBE PDF icons, to facilitate exporting datashown in views to a report center system that is configured tofacilitate generating reports in the form of electronic documents.Embodiments facilitate creating reports in which the organization ofpages is controlled and source data from a table view is gracefullyfitted into the report pages rather than appearing as a directcut-and-paste without appropriate fitting or formatting. In oneembodiment, selecting the Export widget 424 and an ADOBE PDF icon causesdisplaying a report selection dialog. In an embodiment, the reportselection dialog comprises a list of previously created and savedreports. View computation unit 206 is configured, in response toselection of a particular report in the list of previously created andsaved reports, to display a page list identifying all pages that havebeen previously defined in the selected report.

Selecting a particular page in the page list may cause view computationunit 206 to trigger execution of report unit 209 (FIG. 2A). In response,report unit 209 causes displaying a report creation user interface (alsoreferred to herein as a “report editor user interface”). Examples ofreport generation and/or editing user interfaces are described in U.S.Provisional Patent Application No. 62/046,644, filed Sep. 5, 2014, andtitled “SYSTEMS AND USER INTERFACES FOR DYNAMIC AND INTERACTIVE REPORTGENERATION AND EDITING BASED ON AUTOMATIC TRAVERSAL OF COMPLEX DATASTRUCTURES,” the entire disclosure of which is hereby made part of thisspecification as if set forth fully herein and incorporated by referencefor all purposes, for all that it contains.

In various embodiments, the report editor user interface may include aContext link that may be used to specify a context for the report interms of a named individual or legal entity (for example, the Contextlink may be similar to portion 1610 of FIG. 16 described below, in thatthe Context link may enable the user to select a particularperspective). As noted above, a Context may include a Perspective (anindividual, legal entity, and/or group) and/or a date or date range. Thereport editor user interface may further include a link by which theuser may specify a particular date and/or date range. The report unit209 is configured to receive user input selecting the Context link andto display a list of other individuals or legal entities that areassociated with the current logged in user and/or Perspectives that maybe selected for the Context. In response to receiving a selection of adifferent individual or legal entity, the report view is re-computed andre-rendered from the perspective of the next Context. Re-computationinvolves re-traversing the graph 202 in the manner described above forgenerating table view 408 of FIG. 4. As described further below, areport view may comprise a plurality of independent widgets for text,tables, and graphics, and in an embodiment changing the Context causeseach widget to perform an independent traversal of graph 202 tore-compute values for display in that widget. Thus, working on a reportinvolves creating and storing metadata that defines the components ofthe report and certain formatting attributes of the report, but notparticular values in the report; instead, the current Context drives atraversal of the graph 202 to generate values for substitution into aview of the report based on the metadata. Moreover, the techniquesherein have the benefit of separating the construction and format of aparticular widget from the underlying data, so that programmatic changesin a widget will result in displaying the widget in updated form whilerendering in correct and timely underlying data based on traversing thegraph 202.

Accordingly, as described above, the interactive user interfaces of thesystem enable non-technical users to quickly and dynamically generateand edit complex reports including tables and charts of data. Thecomplex reports may be automatically and efficiently generated throughaccess and traversal of complex data structures, and calculation ofoutput data based on property values of multiple nodes within thecomplex data structures, all in substantially real-time. By storing thedata as a complex mathematical graph, outputs (for example, a table)need not be stored separately and thereby take additional memory.Rather, the system may render outputs (for example, tables) in real timeand in response to user interactions, such that the system may reducememory and/or storage requirements. Thus, in some embodiments, thesystems and user interfaces described herein may be more efficient ascompared to previous systems and user interfaces.

5.0 EXAMPLE GRAPH TRAVERSAL AND TABLE GENERATION

FIG. 14 is a flowchart showing an example method of the system in whicha table is generated via graph traversal and column factor calculations.In various embodiments, fewer blocks or additional blocks may beincluded in the process of FIG. 14, or various blocks may be performedin an order different from that shown in the figure. Further, one ormore blocks in the figure may be performed by various components of thesystem as described above and below, for example, one or more of viewcomputation unit 106 and/or report unit 109.

Beginning at block 1402, the graph, for example graph 202, is traversedand all the paths associated with the selected context are enumerated.This block is described in further detail above in reference to FIG. 3A.Graph traversal and enumeration of paths may be dependent on aparticular context. For example, a given perspective (for example, anindividual, legal entity, and/or the like) may indicate the locationsfrom which the graph is traversed. An example is described above, andanother example is illustrated in FIGS. 15A-15C. In particular, FIGS.15A-15C illustrate an example traversal of a simplified graph 1502,according to an embodiment of the present disclosure. Referring to FIG.15A, the graph 1502 includes six nodes: Alice (representing anindividual, and which may be referred to as node A), Bob (representingan individual, and which may be referred to as node B), “C” Trust(representing an trust instrument, and which may be referred to as nodeC), Stock “D” (representing a stock instrument, and which may bereferred to as node D), Bond “E” (representing a bond instrument, andwhich may be referred to as node E), and Stock “F” (representing a stockinstrument, and which may be referred to as node F). The relationshipsamong the various nodes of the graph are indicated by the edges.Further, as described above, various attributes and/or properties may beassociated with each of the nodes and/or edges of the graph. Forexample, as described above and below, each of the edges of the graphmay indicate a relationship between the two nodes connected by the edge.In one example, an edge may indicate a value and/or percentage of anasset (for example, a stock, bond, and/or the like) owned by anindividual.

For simplicity of explanation, graph 1502 illustrates a simple graphwith a small number of nodes and no complex relationships among thenodes. However, in various embodiments, and depending on actual datastored in the system, the graph may include hundreds, thousands,millions, or more nodes and/or edges. Further, the graph may includecomplex relationships including loops, and/or the like. Accordingly,identifying paths through a typical graph having thousands or more nodesand edges would not be practical to perform manually, at least for thereasons that it would take an impractical amount of time to perform(e.g., days, weeks, or longer to traverse a large graph) and the processwould be error-prone (e.g., manual traversal of thousands or more nodeswould have a nonzero error rate). Accordingly such processes arenecessarily performed by computing processors and systems, using thevarious methods discussed herein.

According to an embodiment, FIG. 15B illustrates an aspect of traversalof the graph 1502. As described above (and as further described inreference to FIG. 2B), a graph and a context are provided in the processof graph-to-table transformation. In the embodiment of FIG. 15B, thecontext includes the perspective “Bob.” Accordingly, in the example thegraph is traversed from the perspective of Bob so as to generate a tableof information derived from the graph. As further shown in FIG. 15B, an“Asset Type” bucketing factor has been selected by a user (orautomatically by the view computation unit 106 and/or report unit 109,for example). Accordingly, the generated table will include rowscorresponding to assets associated with Bob, and organized according toasset types (as described above). Additionally, an “asset value” columnfactor (also referred to herein as an “asset” column factor) has beenselected. Accordingly, the generated table will include at least onecolumn showing values corresponding to the various rows of the table.

As described above in reference to FIG. 3A, the graph 1502 is traversedso as to enumerate all the paths associated with node B (as node Brepresents Bob). FIG. 15B illustrates all five paths associated withnode B as determined by the system. In various embodiments, each pathmay include nodes and/or edges of the graph that comprise the path inthe graph, as well as any attributes associated with the nodes and/oredges of the path.

Returning now to FIG. 14, each of blocks 1404-1416 describe additionalaspects of the graph-to-table transformation, which is also describedabove in reference to FIG. 3B. Specifically, at block 1404 (roughlycorresponding to blocks 316-330 of FIG. 3B), the various enumeratedpaths are processed based on a selected bucketing factor to create atree (also referred to herein as a “bucketing tree”) of various valuesassociated with the bucketing factor, and paths associated with thosevalues. In an embodiment, the values represented in the bucketing treemay be represented by nodes (also referred to herein as “value nodes”).In the example of graph 1502 (of FIG. 15A), this step is illustrated inFIG. 15C in which the bucketing factor is asset type. As shown, abucketing tree 1512 associated with graph 1502 includes a root node 1514(also referred to herein as a “root value node”) corresponding to allpaths associated with an asset (3, 4, and 5), child nodes 1516 (alsoreferred to herein as child “value nodes”) corresponding to types ofassets (for example, stocks and bonds), and further child nodes 1518corresponding to actual individual assets (for example, Stock “D”, Stock“F”, and Bond “E”). Further, paths associated with each of the nodes areshown. These include, for example, path 4 for Bond “E”, path 3 for Stock“D”, path 5 for Stock “F”, paths 3 and 5 for “Stocks”, path 4 for“Bonds”, and paths 3, 4, and 5 for “All Assets”.

In reference again to FIG. 14, in blocks 1406-1416 each node of thebucketing tree is processed so as to calculate column values to bedisplayed in the table. Some aspects of this process, according to anembodiment, are described above in reference to blocks 331-340 of FIG.3B.

At block 1406, each node (as indicated by loop arrow 1422) of thebucketing tree, including its associated path, is processed. Processingof each node includes, at block 1408, evaluation of the node withrespect to each column factor (as indicated by loop arrow 1424) (forexample, each metric selected by the user including, for example, assetvalue, rate of return, IRR, and/or the like). For each of the columnfactors, at block 1410, each path associated with the node is processed(as indicated by loop arrow 1426) so as to determine, at block 1412, apath value. For example, if the column factor is “asset value,” eachpath associated with the node is processed so as to calculate the assetvalue associated with the path. Then, at block 1414, the path valuescalculated with respect to each of the path associated with the node areaggregated so as to determine a column value. This calculated columnvalue indicates a value of the given column factor with respect to thenode being processed.

For example, in the instance of a bucketing tree node representing anasset class such as “Stocks,” multiple paths may be associated with thenode, each of the paths associated with different stocks. In calculatinga bucketing factor “Asset Value” associated with the node, each of thepaths may be traversed and values of each of the particular stocks arecalculated. Then, all of the calculated values may be aggregated bysummation so as to calculate a total value of all stocks.

In various embodiments, calculation of path values may be accomplishedby referencing data (for example, attributes and/or metadata) associatedwith one or more nodes and/or edges associated with the path. Examplesare given above and below. In some embodiments, attributes and/ormetadata associated with nodes and/or edges of a path may be stored astransaction effects object. Examples of such transaction effectsobjects, including creation of the transaction effects objects andcalculations based on the transaction effects objects are described indetail in U.S. patent application Ser. No. 13/714,319, filed Dec. 13,2012, and titled “Transaction Effects,” the entire disclosure of whichis hereby made part of this specification as if set forth fully hereinand incorporated by reference for all purposes, for all that itcontains.

At block 1416, the each of the calculated column values is inserted intothe table in respective columns associated with the column factors, anda row associated with the processed node of the bucketing tree.

This process is further illustrated with reference to bucketing tree1512 and FIG. 15C. In FIG. 15C, the “value” column factor has beenselected, and the “Stock” node is associated with paths 3 and 5.Accordingly, each of paths 3 and 5 may be individually processed by thesystem so as to determine a value of stocks associated with Bob. Forexample, edges in path 3 may indicate that Bob owns 50% of Trust “C”,and further, Trust “C” has $1000 of Stock “D”. Thus the system maydetermine that Bob owns $500 of Stock “D”. Similarly, the system willdetermine an ownership of Stock “F” with respect to Bob. Next, thesystem aggregates the determined values and the aggregated data isdisplayed in a row and column of the table corresponding to Stocks andvalue.

An example of a table generated by the graph traversal of FIGS. 15A-15Cis shown in FIG. 16. FIG. 16 shows an example user interface 1600including two portions 1610 and 1612. The portion 1610 shows thatcurrently selected perspective 1630 (in this example, Bob), while theportion 1612 shows the table generated based on the traversal describedabove in reference to FIGS. 15A-15C. As shown, the table includes sixrows corresponding to each of the nodes of the bucketing tree 1512 (forexample, Bonds, Stocks, Bond “E”, Stock “D”, Stock “F”, and Total). Thenumbers in the column “Value” are displayed with respect to each of therows, and are determined based on processing of the associated paths, asdescribed above.

Accordingly, in various embodiments the system may automaticallygenerate a table of data associated with a context via rapid traversalof complex graphs of related data items.

As described above, selection of a different context, application offilters, selection of different bucketing factors (for example, changingthe type and/or hierarchical arrangement of rows of the table),selection of different column factors (for example, changing thecalculated information displayed with respect to each row) causes thesystem to automatically re-traverse the graph and regenerate the table.For example, the user may change the context to Alice, may choose toorganize the rows of the table according to geographical location ofassets, and/or may choose to include a column showing Internal Rate ofReturn (IIR) (and/or any other metric). In response, the systemautomatically re-traverses the graph 1502 from the perspective of node Ato determine associated paths, applies the geographical locationbucketing factor to generate a bucketing tree associated with thedetermined paths, and calculate for each of the nodes (and associatedpaths) of the bucketing tree an IIR and/or a value. The system may thengenerate a table including the calculated data.

In various embodiments, the user may select multiple bucketing factorsand may specify a hierarchical relationship among them, as describedabove in reference to FIG. 6, for example. FIG. 17A illustrates andexample bucketing tree 1712 in which a user has specified two bucketingfactors, Asset Type and Geographical Location. Further, the user hasindicated that Geographical Location is to be a sub-categorization ofAsset Type. As shown, the bucketing tree accordingly includes nodescorresponding to the Geographical Location associated with each of theasset types. Further, FIG. 17B illustrates an example user interfacesimilar to the user interface of FIG. 16. The example user interface ofFIG. 17B includes table 1714 showing results of the new categorizationillustrated in FIG. 17A.

In some embodiments, calculation of values associated with each path,and aggregation of multiple path values, varies depending on a columnfactor. For example, when calculating a simple current value of a givenasset or asset type, calculation of path values may comprisemultiplication of a current value of the asset with a number of sharesheld. Further, aggregation of multiple path values in this example maycomprise a summation of all path values to determine a total value ofthe asset or asset type. However, in another example, the calculationand aggregation may differ. Examples of other column factors that mayeach have different path calculation and aggregation include % ofportfolio, active return, alpha, beta, average daily balance, internalrate of return, and/or the like.

6.0 AUTHENTICATION AND PERMISSIONING

As described above, in some embodiments the system may include userauthentication and permissioning. For example, a user of the system maybe required to provide authentication information (for example, ausername and password, a fingerprint scan, and/or the like) whenaccessing the system. Such authentication information may be required bythe system before the user may view one or more of the user interfacesdescribed herein, and/or may generate tables based on particular datastored by the system. In some embodiments, the user's identity may beused to determine particular data of the system which is accessible tothe user. For example, the system may include data associated with manyclients, only some of which are associated with the user. Accordingly,only data related to the clients associated with the user may beavailable via the various user interfaces. Thus, the user's identitymay, in some embodiments, be authenticated before any data is shown tothe user. Permissions data may be associated with the various datastored by the system such that the system may make available to aparticular user only data that is permissioned such that it should bemade available to that particular user.

For example, in reference to FIG. 15A, in some instances a first usermay have permission to view Stock “D” (or particular attributes or othermetadata associated with node D), while a second user may not havepermission to view Stock “D”. Accordingly, while Stock “D” may exist ingraph 1502 no matter whether the first user or the second user is loggedin to the system, when traversing the graph and/or generating tables,Stock “D” may be effectively invisible to the second user. Thus, in thisexample, a table generated for the second user would not include anydata associated with Stock “D”.

Additional examples of permissioning and permissions implementationsthat may be used in conjunction with the present disclosure aredescribed in U.S. Provisional Patent Application No. 62/065,486, filedOct. 17, 2014, and titled “SYSTEM AND ARCHITECTURE FOR ELECTRONICPERMISSIONS AND SECURITY POLICIES FOR RESOURCES IN A DATA SYSTEM,” theentire disclosure of which is hereby made part of this specification asif set forth fully herein and incorporated by reference for allpurposes, for all that it contains.

In some embodiments, the system stores separate graphs associated withvarious clients of a firm (e.g., a wealth management, financial advisor,or investment firm). For example, a firm may have multiple clients, eachof whom may manage one or more portfolios. In order to segregate dataassociated with each of the clients to as to prevent disclosure ofconfidential information, the system may maintain a separate graph foreach of the clients. Such a segregation of graphs may advantageouslyenable protection of each client's data. In some examples, however,multiple clients' graphs may include common data entities/nodes. Forexample, a first client's graph may include Stock A, while a secondclient's graph may similarly include Stock A. In an embodiment, Stock Ain each of the first and second client's graphs may indirectly referencea common Stock A node. Alternatively, the Stock A node in each of thefirst and second client's graphs may reference a common source ofmetadata and/or attributes associated with the Stock (for example,publicly available data such as a stock price). Such indirectreferencing of a common node, and/or referencing a common source ofattributes may advantageously reduce memory requirements of the systemwhile maintaining privacy of each client's graphs.

In some embodiments, the system may include a single graph for multipleclients and/or for all clients of a firm. In these embodiments, thesystem may advantageously prevent disclosure of confidential information(for example, the graph may include data pertaining to a single client,or a subset of the clients on the system) via permissioning (asdescribed above). Further, in these embodiments the system mayadvantageously further reduce memory requirements as redundant data mayfurther be eliminated (for example, a single instance of all assets (forexample, Stock A, etc.) may be maintained by the system).

Additionally, the specialized graph data structure utilized by thesystem enables data security (for example, protection and partitioningof client data) while simultaneously taking advantage of redundant datato reduce memory needs and computation needs. For example, as describedabove, in some embodiments particular data nodes may be shared amongmultiple clients in a common graph, and computations (for example, graphtraversal) for all of the multiple clients may be run on the commongraph, while at the same time permissioning of the common nodes of thegraph for particular clients provides data security.

7.0 GENERATING TABLE VIEWS WITH TIME VARYING ATTRIBUTES

FIGS. 18A-18C illustrate example user interfaces of the system in whichthe user may associate a custom attribute with an asset. Referring toFIG. 18A, according to an embodiment, a user interface is shown that issimilar to the user interface of FIGS. 1A, 1B, 16, and/or 17B, howevervarious attributes (also referred to herein as properties and/ormetadata) associated with a selected asset are displayed and editable bythe user in a sidebar 1802. As shown in FIG. 18A, the user mayinteractively select one or more assets and other items shown in theuser interface so as to view and edit attributes associated with theselected assets and other items via the sidebar 1802. In the exampleshown, the user, via cursor 1802, has selected Security A. Accordingly,the system has displayed various attributes associated with Security Ain the sidebar 1802. Various attributes may be displayed in the sidebarincluding those shown (for example, currency, name, ownership type,asset class, geography, and/or the like), those described above and inreference to FIG. 13, and/or various other attributes including thosethat may be arbitrarily defined by the user (as described below).

As shown in the example user interface of FIG. 18A, the user may selectan Add a Property button 1804 via, for example, cursor 1822 so as to adda new attribute to the selected Security A. FIG. 18B illustrates theexample user interface after the user as selected the Add a Propertybutton 1804. As shown, a dropdown menu 1832 may be displayed listing ascrollable list of various common attributes that may be added to theselected security. The user may additionally search for a describedattribute, and/or arbitrarily specify a custom attribute. FIG. 18Cillustrates the example user interface after the user has selected toadd a “manager” attribute. In response, the system updates the sidebarto include the selected attribute and a field 1842 in which the user mayspecify a value of the added attribute. As shown, the user has specifieda value of “Gary” for the manager attribute.

When a single value is provided for an attribute, the attribute isapplied to the security (or other data item) for all time periods.However, in some embodiments the user may specify multiple valuescorresponding to various time periods for a given attribute. Suchvarying attributes are referred to herein as time varying attributes.Time varying attributes may change at various points in time, and may bespecified by the user and/or determined automatically by the systembased on data received from external data sources. FIG. 19A illustratesexample time varying manager attribute information that may be appliedto the Securities A and B. The example time varying manager attributeapplied to Security A is illustrated via timeline 1902. As shown, thevalue of the attribute from any time in the past up until 2011 is Gary,from 2011 to 2012 is Henry, and from 2012 until anytime in the future isHenry again. The example time varying manager attribute applied toSecurity B is illustrated via timeline 1904. As shown, the value of theattribute for all time is Henry. A single value specified for theattribute may be equivalent to setting a single value for an attributethat is not time varying. The example time varying attributes shown inFIG. 19A are simply for illustrative purposes. Any attributes may bestored by the system, with any number of values for any number of timeperiods. Additionally, as described above, attributes may be stored bythe system by association with graph nodes and/or edges corresponding tothe particular securities (and/or other data items) for which theattributes are given.

FIG. 19B illustrates an example graph 1912 showing values for each ofSecurity A and Security B (as associated with Bob) over time. As shown,timelines 1914 and 1916 illustrate the time periods during which eachsecurity was under management of Gary or Henry with respect to the graph1912. Dotted line 1922 illustrates an indication of the values of eachof Security A and Security B as of 2010-04-15, $20,000 and $10,000respectively. Similarly, dotted line 1924 illustrates an indication ofthe values of each of Security A and Security B as of 2011-04-15,$25,000 and $15,000 respectively. These example values are illustratedin the various example user interfaces described above and below.

Returning to FIG. 18C, the user may specify time varying values for agiven attribute by selecting, for example, Add History button 1844. FIG.20A illustrates an example user interface of the system in which anoptions box 2002 is provided to the user in response to selection of theAdd History button 1844. Via the options box 2002, the user may specifytime varying values for a selected attribute. As shown, the user mayspecify a start date via box 2006 and an attribute value via box 2008for the given start date. The user may add additional values and datesby selecting Add button 2004. Similarly, the user may delete enteredvalues and/or add an arbitrary number of time varying values. It may beobserved the the example values entered by the user in the options box2002 correspond to the values of the example timeline 1902 of FIG. 19A,namely, the manager attribute is specified as Gary until 2011, Henryfrom 2011 to 2012, and Gary again from 2012 on.

While the present disclosure describes time varying attributes with atime period granularity of days (for example, the options box 2002allows the user to specify start days for each value), in someembodiments the system may enable specification of time varying valuesat a finer granularity, for example, hours, minutes, and/or seconds.Similarly, when a finer granularity of time varying values is available,the user may additionally specify contexts with a similar fine timegranularity.

FIGS. 20B-20F illustrate example user interfaces of the system in whichdata is presented to the user in a table format based on the specifiedtime varying manager attribute information described in reference toFIG. 19A. As shown in FIG. 20B, the value of the Manager attribute 2012of the selected security (Security A) is indicated in the sidebar forthe date specified by the given context. In this example, the datespecified is 2010-04-15. Accordingly, the value of the Manager attributeat that time is Gary.

As shown, the user may select the Edit Table button 116 to addinformation to the table including indications of the Manager attribute.FIG. 20C illustrates an options box 2042 that is displayed by the systemin response to selection of the Edit Table button 116. As describedabove, the user may edit the table via the options box 2042 so as tospecify particular groupings of data presented (including a hierarchicalarrangement of the groupings) and particular columns to be displayed inthe table. As also described above, the specified columns correspond tometrics that are to be automatically calculated by the system (via, forexample, graph traversal) and presented in the table. As shown, the userhas selected an Add Column button 2044 and selected to add a Managercolumn 2046. In response to the selection, the system automaticallyre-traverses the graph and generates an updated user interface andtable. FIG. 20D illustrates such an updated table in which Managercolumn 2052 has been added to the table. As shown, the values of theManager attribute associated with each of Security A and Security B forthe selected date (2010-04-15) are displayed in column 2052.

FIG. 20E illustrates an example user interface of the system in whichthe user is further specifying changes to the table via options box2042. As shown, the user has, via Add Grouping button 2066, addedManager 2068 to the groupings and placed it at the top of the hierarchysuch that the assets shown in the table will be organized firstaccording to Manager, second according to Asset Class (also referred toherein as Asset Type), and third by actual Security. Additionally, theuser has edited the displayed columns to remove the Manager column andadd a column 2064 corresponding to Asset Value as of a particular date(in this example, 2010-04-15, the same as the date specified in thecurrent context). In response to the user's selections, the systemre-traverses the graph and updates the table to display the example userinterface of FIG. 20F. As shown in column 2072, the assets (includingSecurity A and Security B) of Bob are now organized in a hierarchicalmanner according to Manager and then Asset Type. Information is providedfor the specified contextual data (in this example 2010-04-15). As thecurrent selected date is the same as the date specified with respect tothe metric of column 2076, the metric/column values displayed in the twocolumns 2074 and 2076 are the same. It may be observed that as SecurityA was managed by Gary as of 2010, Security A is categorized under Gary,while Security B is categorized under Henry.

FIGS. 21A-21C illustrate additional example user interfaces of thesystem in which data is presented to the user in a table format based onthe specified time varying manager attribute information described inreference to FIG. 19A. In FIG. 21A, the user may select the dateselection box 114 to change the date of the displayed context. As shown,the user has changed the date to 2011-04-15. Accordingly, the systemautomatically and dynamically re-traverses the graph and updates theuser interface including the displayed table. As shown in column 2102,as both Security A and Security B are managed by Henry in 2011, both arecategorized under Henry. Additionally, the values displayed in column2104 are updated based on the currently selected date, while the valuesdisplayed in column 2106 remain that same as shown in FIG. 20F. FIG. 21Ais similar to FIG. 1A described above.

Turning to FIG. 21B, the user has again selected the Edit Table button116 to cause the system to display the options box 2042. As shown,options box 2042 additionally includes a Group by historical valuescheckbox 2114, which the user has selected. In various embodiments,selection of the Group by historical values checkbox 2114 causes thesystem to automatically update the user interface (including the tablefor which the option has been selected) via re-traversal of the graph toprovide a unique and compact display of time varying attributeinformation not otherwise shown for a given contextual date. Forexample, the user interface of FIG. 21A may be updated, upon selectionof the Group by historical values checkbox 2114, to the user interfaceof FIG. 1B (also described above). As described above, although theselected date remains 2011-04-15, the assets shown in the table areorganized according to their time varying attribute values (alsoreferred to herein as historical values). Thus, in FIG. 1A, no assetvalue for Security A as of 2010-04-15 is displayed under Henry (seelocation 154), as Henry was not the assigned manager of that asset onthat date. Similarly, no current asset value for Security A is displayedunder Gary (see location 152), as Gary was not the assigned manager ofthat asset on the currently selected date.

Accordingly, selection of the Group by historical values checkbox 2114causes the system to traverse the graph and calculate data based on timevarying attributes associated with various graph nodes and/or edges, anddisplay the calculated data in the user interface. Advantageously,display of time varying data, according to some embodiments, provides amore accurate representation of information that was previouslyavailable. For example, while a given asset may currently be managed bya particular person, particular metrics may not be attributable to thatperson if the person was not actually the manager for the time periodrelevant to the metric. This advantage may be more clearly understood byreference to another example, as shown in FIG. 21C.

FIG. 21C illustrates the user interface in which another metric has beenadded to the table in column 2124 (namely, Time Weighted Return (TWR)since inception), and the contextual date has been updated by the userto 2012-04-15 (as shown in date selection box 114). As shown, column2122 has been updated to indicate the asset values as of 2012-04-15, atwhich time Security A was again managed by Gary. However, a Security Arow remains under Henry as the new metric of column 2124 (TWR sinceinception) spans the entire time period from the current contextual dateto the beginning available data (which includes 2011-2012, the timeperiod when Henry was managing Security A. It is notable that the valuesof the calculated TWR in column 2124 are attributable only to the timeperiods during which the particular assets were managed by each manager.Accordingly, it may easily be observed that the TWR of Security A duringthe time period it was managed by Henry is 4%, while the TWR of SecurityA during the time period that it was managed by Gary is 12%.

FIG. 22A illustrates another example metric in column 2132, namely TWR 5year trailing. TWR 5 year trailing differs from TWR since inception inthat the metric is only calculated over the five years previous to thecurrently selected contextual date. Accordingly, it may be seen that thevalues are generally different from the TWR since inception metric ofFIG. 21C. However, it may be noted that the TWR 5 year trailing ofSecurity A when managed by Henry remains the same, as the relevant timeperiod, 2011-2012, remains the same under either metric. This may bebetter understood with reference to FIG. 22B.

FIG. 22B illustrates calculation of time intervals based on attributeinformation associated with the assets, Security A and Security B.Timeline 2270 illustrates time intervals relevant to Security A whencalculating the metric TWR 5 year trailing (as shown in FIG. 22A).Brackets 2272 show the time intervals associated with the time varyingManager attribute of Security A. These were described above in referenceto FIG. 19A. It is of note that these time intervals are relevant to thecalculation of TWR 5 year trailing for at least two reasons: 1. Becausethe user has selected to view the time varying information associatedwith the assets of the table (for example, by selection of the Group byhistorical values checkbox 2114); and 2. Because the table is grouped bythe Manager attribute, which varies with time for at least one of thedisplayed assets. If either of these two conditions is not true, thecalculation of time intervals described with reference to FIG. 22B wouldnot be necessary for calculation of the given metric (TWR 5 yeartrailing). Brackets 2274 show time intervals associated with the givenmetric, in this example, the five year time period up to the selecteddata (in this example, the contextual date, or 2012-04-15). Brackets2276 show time intervals corresponding to the intersection of theattribute time intervals and the metric (also referred to herein as thecolumn factor) time intervals. These intersected time intervals arereferred to herein as “calculation time intervals” or “calculationintervals” and they are used in the graph traversal process andcalculation of the column values, as described below. It may beunderstood that the calculation time intervals correspond to rows of thetable. For example, the time intervals 2007-04-15 to 2010-12-31, and2012-01-01 to 2012-04-15 may be used to calculate the TWR 5 yeartrailing for Security A as managed by Gary, while the time interval2011-01-01 to 2011-12-31 may be used to calculate the TWR 5 yeartrailing for Security A as managed by Henry.

Similar to timeline 2270, timeline 2280 illustrates time intervalsrelevant to Security B when calculating the metric TWR 5 year trailing.Bracket 2282 shows the time interval associated with the Managerattribute of Security B. Bracket 2284 show time interval associated withthe given metric. And bracket 2286 shows the time interval correspondingto the intersection of the attribute time interval and the metric timeinterval. As described above, the calculation time interval 2286 is usedin the calculation of the metric/column factor for Security B whenmanaged by Henry.

FIG. 22C is a flowchart showing an example method of the system in whichtime intervals associated with a given path and metric are calculated.In various embodiments, fewer blocks or additional blocks may beincluded in the process of FIG. 22C, or various blocks may be performedin an order different from that shown in the figure. Further, one ormore blocks in the figure may be performed by various components of thesystem as described above and below, for example, one or more of viewcomputation unit 106 and/or other aspects of the system.

At block 2272, any time varying attributes relevant to the current tableare determined. As described above, the calculation of metrics based ontime varying attributes is only performed by the system if 1. the userhas selected to view the time varying information associated with theassets of the table (for example, by selection of the Group byhistorical values checkbox 2114); and 2. the table is grouped by anattribute which varies with time for at least one of the displayedassets. Thus, for example, the system determines whether the table isgrouped by an attribute that varies with time for at least one of theassets of the table. If so, the process proceeds to block 2294.

At block 2294, the system determines any time intervals associated withthe given path for which the metric is being calculated. For example, asdescribed above, paths in the mathematical graph may generallycorrespond to rows of the table. Accordingly, time intervals associatedwith the path may be determined such that the given metric may becalculated with respect to the table row. An example is illustrated inFIG. 22B with brackets 2272 in which time intervals are determined forthe time varying manager attribute for Security A (Security Acorresponding to a row of the table/path in the graph). As is describedbelow in reference to FIG. 22D, block 2294 is performed for each of theenumerated paths in the graph such that metric calculations may beperformed with respect to each row of the table. It may be understoodthat there may be not time intervals associated with a given path. Forexample, with respect to Security B of FIGS. 22A-22B, there is not timeinterval associated with a Gary value of the manager attribute (because,for example, Gary never managed Security B). Accordingly, ultimately thecalculated metric is going to be void, and the system may, in someembodiments, leave a blank space in the table for the value, or omit thepath/row completely (as is the case in FIG. 22A as no relevantcalculations pertain to Security B as managed by Gary).

At block 2296, the system determines any time intervals associated withthe given metric/column factor. An example is illustrated in FIG. 22Bwith brackets 2274 in which time intervals are determined for the TWR 5year trailing metric. As is described below in reference to FIG. 22D,block 2296 is performed for each of the metrics/column values of thetable such that metric calculations may be performed with respect toeach column of the table.

At block 2298, the system calculates the intersection of the path timeintervals and the column factor/metric time intervals to determine the“calculation intervals” for the given path and metric. An example isillustrated in FIG. 22B with brackets 2276 in which calculation timeintervals are calculated for TWR 5 year trailing of Security A for eachof two paths: Gary (2007-04-15 to 2010-12-31 and 2012-01-01 to2012-04-15) and Henry (2011-01-01 to 2011-12-31).

Accordingly, as described in reference to FIG. 22C, the system maycalculate “calculation intervals” for each combination of path andmetric/column factor relevant to the table of the user interface.

FIG. 23 is a flowchart showing an example method of the system in whicha table is generated via graph traversal and column factor calculations,including time varying attributes. The flowchart of FIG. 23 includesmany blocks similar to the flowchart of FIG. 14. However, additionalblocks 2303, 2304, and 2306 of the flowchart of FIG. 23 enable thecalculation and display of time varying data (examples of which aredescribed above with respect to FIGS. 1B, 21C, and 22A). In variousembodiments, fewer blocks or additional blocks may be included in theprocess of FIG. 23, or various blocks may be performed in an orderdifferent from that shown in the figure. Further, one or more blocks inthe figure may be performed by various components of the system asdescribed above and below, for example, one or more of view computationunit 106 and/or other aspects of the system.

Blocks 1402, 1404, 1406, 1408, 1410, 1414, and 1416 proceed generally asdescribed above with reference to FIG. 16. A simplified example of theprocess is illustrated by FIGS. 24A-24E with reference to simplifiedgraph 2402 of FIG. 24A (similar to the simplified example of FIGS.15A-15C). Briefly, at block 1402, the graph is traversed so as toenumerate all paths with respect to the selected perspective. In thisexample, the perspective is Bob, and the graph 2402 is traversed so asto enumerate the paths as shown in FIG. 24B. At block 1404, a bucketingtree is generated (as described above) based on the selected bucketingfactors. In this example, the bucketing factors include a hierarchicalarrangement of Manager and then Asset Type. Accordingly, an examplebucketing tree 2412 is generated as shown in FIG. 24C. As shown, thepaths are organized into various value nodes corresponding to rows thatwill be inserted in the table. Values nodes 2414 include all managers,value nodes 2416 include each value of the manager attribute found inthe paths, value nodes 2418 include asset types found in the paths, andvalue nodes 2420 include each of the individual assets.

As described above, at blocks 1406, 1408, and 1410, each value node ofthe bucketing tree is processed so as to calculate each of the columnvalues associated with that value node (see block 1416), each columnfactor associated with a given value node is processed so as tocalculate the relevant column value, which relevant column value iscalculated as each path associated with a given value node is processedso as to generate a path value (see block 1416) that may be aggregatedto calculate the relevant column value (see block 1414).

Within the processing of each path associated with a value node as shownin blocks 1410 and the loop arrow 1426, the path values are calculatedin blocks 2302, 2304, and 2306 taking into account time varyingattributes. In block 2302, first the calculation intervals associatedwith the given path and column factor are calculated as described inreference to FIG. 22C. This process is illustrated in the simplifiedexample in FIGS. 24D and 24E. In particular, in FIG. 24D the timevarying attributes relevant to the current table are determined (asdescribed in reference to block 2292 of FIG. 22C). In this example, theonly time varying attribute that is relevant is the Manager attribute.Then, in FIG. 24E, the calculation intervals are determined for each ofthe paths for the given column factors (as described in reference toblocks 2294, 2296, and 2298 of FIG. 22C). In the example of FIG. 24E,the given column factor is TWR 5 year trailing, and the calculations ofeach of the time intervals relevant to each path were described inreference to FIGS. 22B and 22C. For various values nodes of thebucketing tree associated with multiple paths, the intervals are furtherintersected. Thus, for example, the Henry value node 2480 is associatedwith both paths 3 and 4 as calculated with respect to value nodes 2484and 2486, and thus the relevant calculation interval is 2007-04-15 to2012-04-15 (as this is the intersection of 2011-01-01 to 2011-12-31associated with value node 2484 and 2007-04-14 to 2012-04-15 associatedwith value node 2486). Similarly, each of values nodes 2474, 2476, and2478 is associated with calculation intervals calculated as describedabove in reference to FIG. 22B (2007-04-15 to 2010-12-31 and 2012-01-01to 2012-04-15).

Having calculated the calculation intervals associated with eachcombination of value node and column factor, in block 2304, for eachcalculation interval of the relevant value node and column factor beingdetermined, an interval value is calculated. The interval value iscalculated similar to the calculation of the path value described abovein reference to block 1412 of FIG. 14. In particular, the relevant pathof the graph is traversed and a path value is calculated based onattributes associated with relevant nodes and/or edges of the graph inthe path, taking into account the calculation intervals. For example,suppose the TWR 5 year trailing of value node 2486 (of FIG. 24E) is tobe calculated. The relevant paths include only path 4, and thecalculation intervals including only 2007-04-14 to 2012-04-15.Accordingly, path 4 of the graph 2402 is traversed, including nodes B,C, and E, so as to determine, for Bob's investment in Security B, whatthe TWR is from 2007-04-14 to 2012-04-15. This calculation accounts for,for example, any incremental investments or sales made by Bob within thecalculation interval (which are indicated by attributes associated withedges connecting Bob (node B) to “C” Trust (node C) and “C” Trust (nodeC) to Security B (node E) in graph 2402), and any changes in the valueof Security B within the calculation interval (which are indicated byattributes associated with node B). Any other metrics may be calculatedby the system as described above in an analogous manner for eachapplicable calculation interval.

At block 2306, the calculation interval values calculated in block 2304are aggregated so as to determine a total path value. In the exampleabove in which the path value is calculated for value node 2486, onlyone calculation interval is represented so no aggregation is needed (forexample, the calculation interval value will be equal to the pathvalue). Accordingly, the system determines a TWR 5 year trailing forSecurity B that is attributable to Henry (for example, 9% as shown inFIG. 22A). However, when multiple calculation intervals are associatedwith a path (as is the case with, for example, value node 2478) thecalculation interval values for each are aggregated so as to determine atotal path value. For example, in the case of TWR 5 year trailing forvalue node 2478, a value is determined for each time interval 2007-04-15to 2010-12-31 and 2012-01-01 to 2012-04-15. Then the values areaggregated to arrive at a total TWR 5 year trailing for Security A thatis attributable to Gary (for example, 8% as shown in FIG. 22A).

As described above, any metrics may be calculated by the system, and TWRand asset value are only provided as examples. Examples of other metricsinclude rate of return, IRR, cash flow, average daily balance, and/orthe like. Various metrics may be associated with particular intervalvalue aggregation techniques and/or path value aggregation techniques.For example, calculation of IRR for disparate time intervals may includecalculation of IRR for each individual time interval (accounting forcash flows during those time intervals), followed by a designation ofartificial cash flows for the start and end of each time interval suchthat and IRR across all the time intervals may be calculated. Othersimilar process may be applied to interval value aggregation and/or pathvalue aggregation for various other metrics.

As mentioned above, when no calculation intervals are determined to beassociated with a value node, no entry is provided in the table, and novalue node may be represented in the bucketing tree (for example, novalue node is included in the bucketing tree of FIG. 24E correspondingto Security A as managed by Gary).

Advantageously, according to some of the embodiments described herein,the same graph traversal process as described with reference to FIG. 14may be adapted to account for time varying attributes, as described inreference to FIG. 23. In particular, the path value calculation processmay be expanded to include consideration of time intervals associatedwith each path.

In some embodiments, values of time varying attributes associated with aparticular data item may overlap. For example, a particular asset may bemanaged by two managers during a particular period of time, and also byeach of the managers individually during other different periods oftime. The graph traversal process in such embodiments proceeds asdescribed above, however certain time intervals may overlap calculationinterval determination.

Thus, the system advantageously, according to some embodiments,automatically calculates complex data based on time varying attributesvia graph traversal. As described above, the user may advantageouslyedit the table so as to change the categorization, add or remove columnfactors, apply filters, and/or the like, and in response the systemautomatically and dynamically re-traverses the graph, calculates newdata values, and updates the table of the user interface. No previoussystems have been as powerful, flexible, and/or processor and memoryefficient. Further, the system compactly presents complex time varyinginformation to the user more efficiently than previous systems andmethods.

While the present disclosure has largely described the system withrespect to a Manager time varying attribute, it is to be understood thatany other attribute may be time varying, and the table may becategorized according to any other attribute. As an example, ageographical time varying attribute may be applied to assets. Forexample, a particular stock may initially be considered a Europeanstock. However, over time the stock may transition to being a primarilyUS stock. Accordingly, the geography attribute associated with the stockmay vary with time, and the user may organize the table according togeography of assets (and thus metrics will be calculated by the systembased on the time varying geography attribute). Numerous other examplesmay be provided and are intended to fall within the scope of the presentdisclosure.

8.0 DATA CACHING

In various embodiments the system may cache data generated by graphtraversals so as to speed up computation of data for table generationand/or speed up graph traversals. For example, in various embodimentsthe system may automatically store enumerated paths, calculatedbucketing trees, and/or calculated column values. Accordingly, thesystem may, in future graph traversals, and when no changes have beenmade to at least portions of the graph that would invalidate suchcaches, utilize such caches to speed up computations. Accordingly, inthese embodiments the system may reduce computational needs and speed upgeneration of tables and user interfaces requested by the user.

In another example, the system may cache calculated calculationintervals, calculated calculation interval values, path values, and/orthe like. Further, the system may automatically determine that two ormore sets of calculation intervals are equal to one another. Forexample, calculation of the following two metrics have the sameassociated time intervals: Current IRR (wherein the current date rangeis 2001-2002) and IRR 1 year trailing (wherein the current date is2002). The system may automatically determine that the two timeintervals are the same, and may therefore cache calculation intervalvalue calculations from one to be used with respect to the other.

9.0 HARDWARE OVERVIEW

According to various embodiments, the techniques described herein areimplemented by one or more special-purpose computing devices. Thespecial-purpose computing devices may be hard-wired to perform thetechniques, or may include digital electronic devices such as one ormore application-specific integrated circuits (ASICs) or fieldprogrammable gate arrays (FPGAs) that are persistently programmed toperform the techniques, or may include one or more general purposehardware processors programmed to perform the techniques pursuant toprogram instructions in firmware, memory, other storage, or acombination. Such special-purpose computing devices may also combinecustom hard-wired logic, ASICs, or FPGAs with custom programming toaccomplish the techniques. The special-purpose computing devices may bedesktop computer systems, portable computer systems, handheld devices,networking devices or any other device that incorporates hard-wiredand/or program logic to implement the techniques.

For example, FIG. 25 is a block diagram that illustrates a computersystem 2600 upon which various embodiments of the invention may beimplemented. Computer system 2600 includes a bus 2602 or othercommunication mechanism for communicating information, and a hardwareprocessor 2604 coupled with bus 2602 for processing information.Hardware processor 2604 may be, for example, a general purposemicroprocessor. In various embodiments, one or more of the memory 200,data repository 204, table view 205, view computation unit 206,rendering unit 207, report unit 209, graph model logic 212, custodianinterface unit 213, and/or the like, may be implemented on the computersystem 2600. For example, the various aspects of the systems describedin reference to FIG. 2A may be stored and/or executed by the computersystem 2600.

Computer system 2600 also includes a main memory 2606, such as a randomaccess memory (RAM) or other dynamic storage device, coupled to bus 2602for storing information and instructions to be executed by processor2604. Main memory 2606 also may be used for storing temporary variablesor other intermediate information during execution of instructions to beexecuted by processor 2604. Such instructions, when stored innon-transitory storage media accessible to processor 2604, rendercomputer system 2600 into a special-purpose machine that is customizedto perform the operations specified in the instructions.

Computer system 2600 further includes a read only memory (ROM) 2608 orother static storage device coupled to bus 2602 for storing staticinformation and instructions for processor 2604. A storage device 2610,such as a magnetic disk or optical disk, is provided and coupled to bus2602 for storing information and instructions.

Computer system 2600 may be coupled via bus 2602 to a display 2612, suchas a cathode ray tube (CRT), for displaying information to a computeruser. An input device 2614, including alphanumeric and other keys, iscoupled to bus 2602 for communicating information and command selectionsto processor 2604. Another type of user input device is cursor control2616, such as a mouse, a trackball, or cursor direction keys forcommunicating direction information and command selections to processor2604 and for controlling cursor movement on display 2612. This inputdevice typically has two degrees of freedom in two axes, a first axis(e.g., x) and a second axis (e.g., y), that allows the device to specifypositions in a plane.

Computer system 2600 may implement the techniques described herein usingcustomized hard-wired logic, one or more ASICs or FPGAs, firmware and/orprogram logic which in combination with the computer system causes orprograms computer system 2600 to be a special-purpose machine. Accordingto one embodiment, the techniques herein are performed by computersystem 2600 in response to processor 2604 executing one or moresequences of one or more instructions contained in main memory 2606.Such instructions may be read into main memory 2606 from another storagemedium, such as storage device 2610. Execution of the sequences ofinstructions contained in main memory 2606 causes processor 2604 toperform the process steps described herein. In alternative embodiments,hard-wired circuitry may be used in place of or in combination withsoftware instructions.

The term “storage media” as used herein refers to any non-transitorymedia that store data and/or instructions that cause a machine tooperation in a specific fashion. Such storage media may comprisenon-volatile media and/or volatile media. Non-volatile media includes,for example, optical or magnetic disks, such as storage device 2610.Volatile media includes dynamic memory, such as main memory 2606. Commonforms of storage media include, for example, a floppy disk, a flexibledisk, hard disk, solid state drive, magnetic tape, or any other magneticdata storage medium, a CD-ROM, any other optical data storage medium,any physical medium with patterns of holes, a RAM, a PROM, and EPROM, aFLASH-EPROM, NVRAM, any other memory chip or cartridge.

Storage media is distinct from but may be used in conjunction withtransmission media. Transmission media participates in transferringinformation between storage media. For example, transmission mediaincludes coaxial cables, copper wire and fiber optics, including thewires that comprise bus 2602. Transmission media can also take the formof acoustic or light waves, such as those generated during radio-waveand infra-red data communications.

Various forms of media may be involved in carrying one or more sequencesof one or more instructions to processor 2604 for execution. Forexample, the instructions may initially be carried on a magnetic disk orsolid state drive of a remote computer. The remote computer can load theinstructions into its dynamic memory and send the instructions over atelephone line using a modem. A modem local to computer system 2600 canreceive the data on the telephone line and use an infra-red transmitterto convert the data to an infra-red signal. An infra-red detector canreceive the data carried in the infra-red signal and appropriatecircuitry can place the data on bus 2602. Bus 2602 carries the data tomain memory 2606, from which processor 2604 retrieves and executes theinstructions. The instructions received by main memory 2606 mayoptionally be stored on storage device 2610 either before or afterexecution by processor 2604.

Computer system 2600 also includes a communication interface 2618coupled to bus 2602. Communication interface 2618 provides a two-waydata communication coupling to a network link 2620 that is connected toa local network 2622. For example, communication interface 2618 may bean integrated services digital network (ISDN) card, cable modem,satellite modem, or a modem to provide a data communication connectionto a corresponding type of telephone line. As another example,communication interface 2618 may be a local area network (LAN) card toprovide a data communication connection to a compatible LAN. Wirelesslinks may also be implemented. In any such implementation, communicationinterface 2618 sends and receives electrical, electromagnetic or opticalsignals that carry digital data streams representing various types ofinformation.

Network link 2620 typically provides data communication through one ormore networks to other data devices. For example, network link 2620 mayprovide a connection through local network 2622 to a host computer 2624or to data equipment operated by an Internet Service Provider (ISP)2626. ISP 2626 in turn provides data communication services through theworld wide packet data communication network now commonly referred to asthe “Internet” 2628. Local network 2622 and Internet 2628 both useelectrical, electromagnetic or optical signals that carry digital datastreams. The signals through the various networks and the signals onnetwork link 2620 and through communication interface 2618, which carrythe digital data to and from computer system 2600, are example forms oftransmission media.

Computer system 2600 can send messages and receive data, includingprogram code, through the network(s), network link 2620 andcommunication interface 2618. In the Internet example, a server 2630might transmit a requested code for an application program throughInternet 2628, ISP 2626, local network 2622 and communication interface2618.

The received code may be executed by processor 2604 as it is received,and/or stored in storage device 2610, or other non-volatile storage forlater execution.

10.0 ADDITIONAL EMBODIMENTS

Some embodiments have been described above in reference to tablegenerations. However, it is to be understood that the system maysimilarly generate charts, graphs, and/or other types of informationdisplay via graph traversal.

Advantageously, according to various embodiments the system maycalculate data (via complex graph traversal described herein) andprovide a unique and compact display of calculated data based on timevarying attributes associated with the calculated data. Further, thesystem may calculate time intervals applicable to calculations ofvarious metrics. Accordingly, the system may determine a set of timeintervals associated with the metric, a set of time intervals associatedwith applicable time varying attributes of graph data, and determine inintersection of the two sets of time intervals. The calculatedintersection of the sets of time intervals may then be inputted into thecomplex graph traversal process to calculate metric values for displayin compact and efficient user interfaces of the system. Thus,advantageously, in various embodiments, large amounts of data areautomatically and dynamically calculated interactively in response touser inputs, and the calculated data is efficiently and compactlypresented to a user by the system.

Embodiments of the present disclosure have been described that relate tointeractive user interfaces for enabling non-technical users to quicklyand dynamically generate and edit complex reports including tables andcharts of data. The complex reports may be generated through automaticcalculation of applicable time intervals, access and traversal ofcomplex data structures, and calculation of output data based onproperty/attribute values of multiple nodes and/or edges within suchcomplex data structures, all in substantially real-time. The system mayeliminate the need for a skilled programmer to generate a customizeddata and/or a report. Rather, the system may enable an end-user tocustomize, generate, and interact with complex data in multiple contextsautomatically. Accordingly, embodiments of the present disclosure enabledata generation and interaction in fewer steps, result in fastergeneration of complex data, consume less processing and/or memoryresources than previous technology, permit users to have less knowledgeof programming languages and/or software development techniques, and/orallow less technical users or developers to create outputs (such astables and/or reports) than the user interfaces described above. Thus,in some embodiments, the systems and user interfaces described hereinmay be more efficient as compared to previous systems and userinterfaces.

This application includes descriptions of various user interfacecomponents (e.g. tables, graphs, etc.), some of which may be generatedusing certain software libraries licensed under an open source copyrightlicense. Such components are included herein as examples of userinterface components which may be used or exchanged, in otherembodiments, with other similar components that are not licensed underan open source copyright license. Nothing in any such open sourcecopyright licenses or the inclusion of these user interface componentsherein should be construed in any way as a license, implied orotherwise, under any patents that may result from the presentapplication.

While the foregoing is directed to various embodiments, other andfurther embodiments may be devised without departing from the basicscope thereof. For example, aspects of the present disclosure may beimplemented in hardware or software or in a combination of hardware andsoftware. An embodiment of the disclosure may be implemented as aprogram product for use with a computer system. The program(s) of theprogram product define functions of the embodiments (including themethods described herein) and may be contained on a variety ofcomputer-readable storage media. Illustrative computer-readable storagemedia include, but are not limited to: (i) non-writable storage media(e.g., read-only memory devices within a computer such as CD-ROM disksreadable by a CD-ROM drive, flash memory, ROM chips or any type ofsolid-state non-volatile semiconductor memory) on which information ispermanently stored; and (ii) writable storage media (e.g., hard-diskdrive or any type of solid-state random-access semiconductor memory) onwhich alterable information is stored. Each of the processes, methods,and algorithms described in the preceding sections may be embodied in,and fully or partially automated by, code modules executed by one ormore computer systems or computer processors comprising computerhardware. The processes and algorithms may alternatively be implementedpartially or wholly in application-specific circuitry.

The various features and processes described above may be usedindependently of one another, or may be combined in various ways. Allpossible combinations and subcombinations are intended to fall withinthe scope of this disclosure. In addition, certain method or processblocks may be omitted in some implementations. The methods and processesdescribed herein are also not limited to any particular sequence, andthe blocks or states relating thereto can be performed in othersequences that are appropriate. For example, described blocks or statesmay be performed in an order other than that specifically disclosed, ormultiple blocks or states may be combined in a single block or state.The example blocks or states may be performed in serial, in parallel, orin some other manner. Blocks or states may be added to or removed fromthe disclosed example embodiments. The example systems and componentsdescribed herein may be configured differently than described. Forexample, elements may be added to, removed from, or rearranged comparedto the disclosed example embodiments.

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

The term “comprising” as used herein should be given an inclusive ratherthan exclusive interpretation. For example, a general purpose computercomprising one or more processors should not be interpreted as excludingother computer components, and may possibly include such components asmemory, input/output devices, and/or network interfaces, among others.

The term “continuous” as used herein, is a broad term encompassing itsplain an ordinary meaning and, as used in reference to various types ofactivity (for example, scanning, monitoring, logging, and the like),includes without limitation substantially continuous activity and/oractivity that may include periodic or intermittent pauses or breaks, butwhich accomplish the intended purposes described (for example,continuous scanning may include buffering and/or storage of data that isthereafter processed, for example, in batch and/or the like).

Any process descriptions, elements, or blocks in the flow diagramsdescribed herein and/or depicted in the attached figures should beunderstood as potentially representing modules, segments, or portions ofcode which include one or more executable instructions for implementingspecific logical functions or steps in the process. Alternateimplementations are included within the scope of the embodimentsdescribed herein in which elements or functions may be deleted, executedout of order from that shown or discussed, including substantiallyconcurrently or in reverse order, depending on the functionalityinvolved, as would be understood by those skilled in the art.

It should be emphasized that many variations and modifications may bemade to the above-described embodiments, the elements of which are amongother acceptable examples. All such modifications and variations areintended to be included herein within the scope of this disclosure. Theforegoing description details certain embodiments of the invention. Itwill be appreciated, however, that no matter how detailed the foregoingappears in text, the invention may be practiced in many ways. As is alsostated above, it should be noted that the use of particular terminologywhen describing certain features or aspects of the invention should notbe taken to imply that the terminology is being re-defined herein to berestricted to including any specific characteristics of the features oraspects of the invention with which that terminology is associated. Thescope of the invention should therefore be construed in accordance withthe appended claims and any equivalents thereof.

What is claimed is:
 1. A computing system comprising: a computerreadable storage medium configured to store program instructions; and acomputer processor configured to execute the program instructions,wherein executing the program instructions causes the computing systemto: generate user interface data useable for rendering a user interfaceon a computing device, the user interface including: a table includingrows and columns, wherein at least one of the rows corresponds to afirst data item or a first group of data items, and wherein at least oneof the columns corresponds to a metric calculable with respect torespective data items or groups of data items; traverse a graph-baseddata structure from a first node of the graph-based data structure anddetermine a set of paths within the graph-based data structure that areassociated with the first node; generate a bucketing tree comprisingvalue nodes, wherein each respective value node corresponds to arespective row of the table and is associated with respective paths ofthe set of paths that are associated with the respective row; for eachcombination of value node of the bucketing tree and metric of the table:determine time intervals associated with paths associated with the valuenode, wherein the time intervals associated with the paths are based atleast in part on information from the graph-based data structure;determine time intervals associated with the metric; calculate, for eachpath associated with the value node, one or more calculation intervalsbased on a combination of the time intervals associated with the metricand the time intervals associated with the paths associated with thevalue node; and based at least in part on the one or more calculationintervals, determine and aggregate path values associated with the valuenode to determine a metric value; and include the metric values in thetable.
 2. The computing system of claim 1, wherein determining the pathvalues associated with the value node comprises, for each pathassociated with the value node: calculating, based on the metric, aninterval value for each respective calculation interval associated withthe path; and aggregating the respective interval values associated withthe path to determine respective path values.
 3. The computing system ofclaim 1, wherein the user interface further includes an input elementthat enables a user to input time-varying attribute information forassociation with a node of the graph-based data structure, wherein thetime-varying attribute information includes at least two attributevalues and time intervals associated with each of the at least twoattribute values.
 4. The computing system of claim 1, wherein the rowsof the table are arranged hierarchically according to a user-definedcategorization of one or more attributes associated with nodes of thegraph-based data structure.
 5. The computing system of claim 4, whereinthe user interface further includes an input element that enables a userto input the categorization of the one or more attributes associatedwith nodes of the graph-based data structure.
 6. The computing system ofclaim 5, wherein the user interface further includes a second inputelement that enables the user to input one or more metrics to beassociated with the table.
 7. The computing system of claim 6, whereinthe one or more metrics include at least one of: asset value, TWR, IRR,rate of return, cash flow, or average balance.
 8. The computing systemof claim 1, wherein the user interface further includes a secondselection element that enables the user to select a date, wherein therespective one or more time intervals associated with the respectivemetrics are determined at least partially based on the date.
 9. Thecomputing system of claim 1, wherein traversing the graph-based datastructure comprises: traversing, from the first node, any edges and/orother nodes connected directly or indirectly with the first node;determining, based on the traversal, any non-circular paths in thegraph-based data structure connected to the first node; and designatingthe determined non-circular paths as the paths associated with the firstnode.
 10. The computing system of claim 9, wherein at least two edges ofthe graph-based data structure are part of a circular reference from thefirst node back to the first node, and wherein traversing thegraph-based data structure further comprises determining whether twosequences of two or more traversed nodes are identical, and if so,backtracking the traversal and moving to the next adjacent node or edge.11. The computing system of claim 10, wherein each of the paths includeat least one node and at least one edge of the graph-based datastructure.
 12. The computing system of claim 1, wherein at least onecolumn of the table corresponds to an asset value metric, and whereincalculating, based on the asset value metric, a respective intervalvalue for each calculation interval associated with the path comprisesdetermining a monetary value associated with the edges and/or nodes ofthe path for each calculation interval.
 13. The computing system ofclaim 12, wherein aggregating the respective interval values associatedwith the path to determine respective path values comprises summing eachof the interval values.
 14. The computing system of claim 1, whereinexecuting the program instructions further causes the computing systemto, for each combination of value node of the bucketing tree and metricof the table: determine that no calculation intervals are associatedwith a given path associated with the value node and a given metric; andinsert a blank space into a cell of the table corresponding to the rowassociated with the value node and the column associated with the givenmetric.
 15. The computing system of claim 1, wherein the graph-baseddata structure comprises a plurality of nodes and edges, wherein atleast some of the nodes store information associated with respectivedata items, wherein at least some of the edges store respectiverelationships between two or more of the nodes, wherein respectivepluralities of attributes are associated with at least some of the nodesand at least some of the edges, and wherein at least one of the nodes isassociated with a time-varying attribute.
 16. The computing system ofclaim 1, wherein executing the program instructions further causes thecomputing system to: receive, via the user interface, an indication of aperspective of a plurality of perspectives, wherein the first node fromwhile the graph-based data structure is traversed is associated with theperspective.
 17. A computing system comprising: a computer readablestorage medium configured to store program instructions; and a computerprocessor configured to execute the program instructions, whereinexecuting the program instructions causes the computing system to:generate user interface data useable for rendering a user interface on acomputing device, the user interface including a table including aplurality of cells associated with various combinations of data itemsand metrics; determine a first node of a graph-based data structureassociated with the table; traverse the graph-based data structure fromthe first node to determine a set of paths within the graph-based datastructure that are associated with the first node; for each of one ormore cells of the plurality of cells of the table: determine paths ofthe set of paths associated with the cell; determine time intervalsassociated with paths associated with the cell, wherein the timeintervals associated with the paths are based at least in part oninformation from the graph-based data structure; determine a metricassociated with the cell; determine time intervals associated with themetric; calculate, for each path associated with the cell, one or morecalculation intervals based on a combination of the time intervalsassociated with the metric and the time intervals associated with thepaths associated with the cell; and based at least in part on the one ormore calculation intervals, determine and aggregate path valuesassociated with the cell to determine a metric value for the cell. 18.The computing system of claim 17, wherein determining the path valuesassociated with the cell comprises, for each path associated with thecell: calculating, based on the metric, an interval value for eachrespective calculation interval associated with the path; andaggregating the respective interval values associated with the path todetermine respective path values.
 19. The computing system of claim 17,wherein the user interface further includes a second selection elementthat enables the user to select a date, wherein the respective one ormore time intervals associated with the respective metrics aredetermined at least partially based on the date.
 20. The computingsystem of claim 17, wherein traversing the graph-based data structurecomprises: traversing, from the first node, any edges and/or other nodesconnected directly or indirectly with the first node; determining, basedon the traversal, any non-circular paths in the graph-based datastructure connected to the first node; and designating the determinednon-circular paths as the paths associated with the first node.